If QPS > 2000 I am using multiple hosts for application which is shooting
requests to cache.
If benchmark is the bottleneck, we shouldn't see drop from 2600 to 2200
when we go from 1 to 3 node cluster.
On Fri, Jan 3, 2020 at 11:24 AM Rajan Ahlawat
wrote:
> Hi Mikhail
>
> could you please share t
Hi Mikhail
could you please share the benchmark code with us?
I am first filling up around a million records in cache. Then through
direct cache service classes, fetching those records randomly.
do you run queries against the same amount of records each time?
Yes, 2600 QPS means, it picks 2600 re
Hi - We are using "BACKGROUND" as the walmode. Is that a problem?
Thanx and Regards,
KR Kumar
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Rajan,
could you please share the benchmark code with us?
do you run queries against the same amount of records each time?
what host machines do you use for your nodes? when you say that you have 5
nodes, does it mean that you use 5 dedicates machines for each node?
Also, it might be that the b
Hi Ilya - The other thread looks like is also ignite, here is the thread dump
reference of the thread
"Thread-687" #2758 daemon prio=5 os_prio=0 tid=0x7f2afc00d800 nid=0x897f
runnable [0x7f299bffe000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.FileDispatcherImpl.pread0(Nativ
-- Forwarded message -
From: Rajan Ahlawat
Date: Thu, Jan 2, 2020 at 4:05 PM
Subject: Ignite partitioned mode not scaling
To:
We are moving from replicated (1-node cluster) to multinode partitioned
cluster.
So assumption was that max QPS we can reach would be more if no. of node
