So I've got the L2 ignite cache working, confirmed with beans, logging, etc, and we're comparing it to our existing ehcache implementation. Unfortunately, so far it seems to be running far fewer operations per second than the ehcache version. However, it does seem like the timing on each cache query (we query by id) is fairly fast, around 5ms per query.
My suspicion is that it's because of how we're doing the batch queries - we get the ids from querying the database with whatever parameters we're getting from the web api, and then we go through each id and try the cache, pooling the rest into a big database query. I'm guessing that, since ignite has the overhead of a network call, even if it's relatively minor when querying for a single id, it could add up to a big delay when querying for hundreds of IDs, compared to hitting local ehcache, even if the ehcache has fewer hits and results in a larger query against the database ultimately. Is there a way to mitigate this problem? Maybe a way to do a batch query against the L2 database? I'm guessing not, but otherwise I'm not sure what else we could do to avoid these performance issues. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Performance-issues-with-Ignite-L2-cache-compared-to-ehcache-tp8069.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
