Your comparison isn't fair. How I understand you comapre IgniteCache#get vs ThreadLocalRandom.current().nextInt(). Am I right?
On Fri, Apr 7, 2017 at 1:46 PM, nragon <[email protected]> wrote: > Same topology as before but now it's using this.cache = > ignite.getOrCreateCache(this.cacheConfig); and this.cache.get(key) > > > Flight recordings: > flight_recording_10228245113_withignite.jfr > <http://apache-ignite-users.70518.x6.nabble.com/file/ > n11807/flight_recording_10228245113_withignite.jfr> > flight_recording_10228245113_withoutignite.jfr > <http://apache-ignite-users.70518.x6.nabble.com/file/ > n11807/flight_recording_10228245113_withoutignite.jfr> > > Job with ignite processed 70k whereas without ignite 378k, in 2minutes. > I know that the second test doesn't require network trips, but still, with > near cache wouldn't it be require only one trip? > > Thanks for the help > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Client-near-cache-with-Apache-Flink-tp11627p11807.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
