Your test runs in single thread, it is have nothing with real-live. Try to measure throughput with utilizing multiple threads and add more server nodes.
Also you can use DataStreamer to fill the cache in effective way [1]. It has an option that allow\disallow overwriting existing entries. [1] https://apacheignite.readme.io/docs/data-streamers##ignitedatastreamer On Thu, May 25, 2017 at 10:39 PM, Andrey Mashenkov < [email protected]> wrote: > 1. It is ok. As in multi-JVM environment you have to make network > round-trip bw client and server. > 2. Local cache can be slower due to contention as it has only single > partition. However, difference in results of Single-JVM and multi-JVM looks > weird to me. > 3. LOCAL means that cache is local for node created it. Unlike other > caches, LOCAL cache can be created on client. > > > On Thu, May 25, 2017 at 12:14 AM, pertsev.ilia <[email protected]> > wrote: > >> Sorry, I forgot to attach thread dumps of client and server processes. >> server-thread-dump.txt >> <http://apache-ignite-users.70518.x6.nabble.com/file/n13125/ >> server-thread-dump.txt> >> client-thread-dump.txt >> <http://apache-ignite-users.70518.x6.nabble.com/file/n13125/ >> client-thread-dump.txt> >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Ignite-2-0-0-read-performance-tp13117p13125.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > > > > -- > Best regards, > Andrey V. Mashenkov > -- Best regards, Andrey V. Mashenkov
