Igniters, This is not the first time I hear about from the community side about the performance issue Kevin is talking below.
In short if a key is not located in a cache then we will go to an underlying storage. This process will be repeated all the time for the same key and this leads to performance degradation in cases when someone needs to check whether a key exists before applying an action. Probably we can use already existed remove queue to cache such queries of non existed keys. Any thoughts & ideas? — Denis > Begin forwarded message: > > From: Zhengqingzheng <zhengqingzh...@huawei.com> > Subject: ignite cache get performance issue when Key, Value not exist > Date: June 8, 2016 at 6:26:17 AM GMT+3 > To: "u...@ignite.apache.org" <u...@ignite.apache.org> > Reply-To: u...@ignite.apache.org > > Hi there, > When I am using cache.get(key) operation to find some value. > I notice that if the key is not exist (neither no record in the database > too), the performance is really slow: about 830ms to return the null result; > BTW, I have set read through and write-behind for this cache, also I add near > cache configurations when create this cache. > > Is it a bug? > > Cheers, > Kevin
