ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Re: How the Ignite Service performance? When we test the CPU soon be occupied 100%
Date Wed, 08 Nov 2017 22:59:22 GMT
On Wed, Oct 25, 2017 at 9:15 AM, aaron@tophold.com <aaron@tophold.com>

> Thanks Andrey!  Now it better, we try to exclude no-core logic to
> separated instances.
> What I learned from last several months using ignite, we should set up
> ignite as a standalone data node, while put my application logic in another
> one.
> Otherwise it will bring too much unstable to my application.  I not sure
> this is the best practice?

It depends on your use case, but I would say that majority of Ignite
deployments have stand-alone data nodes, so there is nothing wrong with
what you are suggesting.

View raw message