Hi, It doesn't metter whether you use get or localPeek for a replicated cache. Both return data stored on a local server node.
If this is just a matter of benchmarking then use getAll instead, set cacheconfiguration.copyonread to false and have more than 1 server nodes in the cluster. Denis On Saturday, May 13, 2017, dany74q <dany...@gmail.com> wrote: > Hey ignite users, > > We're using a replicated, atomic, ignite cache to store system-wide, high > read key value pairs. > There's a often executed scenario (millions per minute) in which we try to > get 15 different keys from said cache - and we use localPeek with > CachePeekMode.ALL to get those. > > While benchmarking said part I've noticed that 1 million localPeeks take > roughly 1.3-1.5 seconds, > same as calling get, getEntry, ScanQuery, and other available methods. > > As the cache is replicated and is available locally, I'd imagine that > localPeek would actually be a bit faster. > Is there any configuration value or usage pattern that we could use to make > it faster ? > > Thanks, > - Danny > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Fastest-way-to-get-multiple-values- > from-replicated-cache-tp12714.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
