Guys, A little observation. We have really many tests which start and stop nodes for each test method. Example is IgniteCacheAbstractQuerySelfTest, it contains about 30 test methods and 3 subclasses. In beforeTest method it starts nodes in afterTest it stops them, while cache setup is the same.
What I'm trying to say is that each test method itself takes milliseconds to run, but grid start/stop takes* more than 5 seconds* for each test method. So from the standpoint of time we are testing grid start/stop all the time. It is not surprising that our tests take very long time to finish. Since we already support dynamic cache start/destroy which are much more fast than grid start/stop, I think we should go through a refactoring and use existing nodes within a suite as much as possible. I believe this can reduce run time of cache related tests like 10 times. Sergi
