Hi Kristian, For testing purposes you can use static IP finder [1] with lists of predefined addresses. Static IP finders are widely used by Ignite unit tests.
Also you can reduced partitions number per cache and IgniteSystemProperties.IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE. More info is here https://apacheignite.readme.io/docs/capacity-planning Next, please consider this topics https://apacheignite.readme.io/docs/performance-tips <https://apacheignite.readme.io/docs/performance-tips> https://apacheignite.readme.io/docs/jvm-and-system-tuning <https://apacheignite.readme.io/docs/jvm-and-system-tuning> Finally, you can avoid nodes restart, caches recreation if it’s ok for you to reuse them among test runs. You can also refer to Ignite unit tests to see something useful. — Denis [1] https://apacheignite.readme.io/v1.6/docs/cluster-config#static-ip-based-discovery > On Jun 14, 2016, at 3:05 PM, 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
