You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Kristian Rosenvold <kr...@apache.org> on 2016/06/14 12:05:02 UTC

Rapidly starting and stopping ignite for integration tests

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

Re: Rapidly starting and stopping ignite for integration tests

Posted by Denis Magda <dm...@gridgain.com>.
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 <kr...@apache.org> 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


Re: Rapidly starting and stopping ignite for integration tests

Posted by Barrett Strausser <ba...@bnrobotics.com>.
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 <kr...@apache.org>
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
>