I'm not sure how rapidly you are starting and stopping Ignite or what facilities you are using. Are you using JUnit like functionality?
I'm made sure to start/stop ignite only once with a class level fixture and setup/teardown only caches' between tests. -b On Tue, Jun 14, 2016 at 8:05 AM, Kristian Rosenvold <[email protected]> wrote: > After adding Ignite to some of our project-specific integration tests, > I was not overly happy with the performance hit this gave us. I > tweaked around a bit, and was able to find a couple of things; > > - Switch to TcpDiscoverySharedFsIpFinder to avoid network service > discovery. > - Reduce initial size of cache through config#setStartSize(100), since > most testcases are small. > > This appears to have *some* effect although I would hardly > characterize it as wonderful, anyone else have any tips ? > > Kristian >
