ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Berry <chriswbe...@gmail.com>
Subject Re: 10X decrease in performance with Ignite 2.0.0
Date Thu, 11 May 2017 15:26:23 GMT

Thank you so much for responding

1. You have 10 nodes with 4 partitioned caches each configured with 2
backups. There are no updates to the caches. Correct? 
Not really, no.

2. Are caches atomic or transactional?
Atomic

3. 5 nodes send compute jobs to the topology of 10 nodes. Correct?
No -- the 5 nodes generate load by hitting a URL on the Ignite Nodes thru a
SLB.
This request contains 200 UUIDs to compute against.
This is the exact same code used in 1.9

4. How many jobs does each task produce?
On average 10 - it depends on how the 200 UUIDs map to the Grid. But the
spread is pretty uniform

5. How many lookups does each job do?
several. it depends on the code path. But at a minimum 5, where these should
all be local to that Node -- so in-memory lookups

6. Will there be any difference between 1.9 and 2.0 if you send the same
number of empty jobs?
None. Exact same code.

7. If job does not do any local processing and just returns result of
cache.localPeek() then it would be fine to replace tasks with
cache.getAll().
It all local processing. And a lot of it. CPU sits around 80-90%. 
The compute data is not small, so we colocate the compute w/ the data. 
NOTE: the Results of the compute is small. a few 100 bytes.




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/10X-decrease-in-performance-with-Ignite-2-0-0-tp12637p12640.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message