Hi Vladimir,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to [email protected] and follow simple instructions in
the reply.
1) I think that it doesn't lead to dramatically performance decrease. Which
version of ignite do you use for your PoC? From 1.9 version you can try
change CacheConfiguration#setQueryParallelism parameter. If you have big
data set it can bring performance improvement.
2) Ignite Cache object is thread safe. I recommend don't close this instance
on each invocate cache operation. Enough only once time to call
getOrCreateCache method and a this instance can be shared beteween
different threads. For example:
// This object is thread safe.
IgniteCache cache = ignite.getOrCreateCache(...);
// Usage template
IgniteCache cache = ignite.getOrCreateCache(...); // Or can be used object
which create above
// Do not need to close cache instance each time for cache operations.
try {
QueryCursor cur = cache.query(...);
List res = cur.getAll();
}
catch (Exception e) {
// Query failed.
}
BTW, could you share simple reproducer which leads to this failure?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-performance-in-multi-threaded-environment-tp15698p15702.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
