Hi Val, When i investigate thread dump of our application, I see a lot of threads waiting on a lock. For example i have 40 threads trying to access same key at same time. So only one of them can read.
I realized this situation because, we have switched our cache provider to ignite and see some performance issues on cache operations. I will try to share my benchmark results. By the way, what is the maximum get operation tps for a ignite cache ? Thanks. -Tolga On Tue, Nov 22, 2016 at 10:19 PM, vkulichenko <[email protected] > wrote: > Hi, > > Yes, Ignite acquires a short-time Java-level lock on entry each time you > access it (either read or write). However, any concurrent updates or reads > of different will not interfere with each other. > > Why do you think this is causing a performance issue? > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Blocked-get-operation-problem-tp9133p9134.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- *Tolga KAVUKÇU*
