ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergi Vladykin <sergi.vlady...@gmail.com>
Subject Re: Query performance
Date Thu, 27 Aug 2015 21:07:49 GMT
Definitely you should try key/value route. With batch operations like
IgniteCache.invokeAll it must be faster than SQL queries, though it still
will be slower than a simple cache put.


2015-08-27 22:46 GMT+03:00 javadevmtl <java.dev.mtl@gmail.com>:

> Anyways I think I will go down the key/value route it's so much faster.
> 1- In the query approach I was able to do atomic operations since each
> request yielded a new entry in the cache and I never had to update. But
> queries for now seem a bit slow.
> 2- Using key/value approach speed of put is alot faster but now I have to
> worry about possibly updating same key multiple times. But entry processor
> seems to do what I need.
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Re-Query-performance-tp1009p1168.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message