Also, as long as you're on Java, you can add the Ignite thick client to the comparison list. It can behave faster for your workload.
- Denis On Mon, Oct 12, 2020 at 6:14 AM Pavel Tupitsyn <ptupit...@apache.org> wrote: > It depends. The only way to tell is to measure and profile your specific > use case. > > What I'm trying to say is: > 1. Start with one instance - low complexity, low overhead. > 2. If performance needs improvement, and Ignite is determined to be a > bottleneck, > consider trying multiple instances, this may help in some cases. > > > On Mon, Oct 12, 2020 at 3:59 PM midulaj <midu...@gmail.com> wrote: > > > Thanks Pavel, > > > > How can we categorize the high load scenarios in the case of Ignite..If > my > > requests to Ingnite are more than 1000 per second then can i take it as a > > high-load or i can consider more figures for high load > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >
