sense for us,
unfortunately. Failure, however, is always an option.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Performance-issues-with-Ignite-L2-cache-compared-to-ehcache-tp8069p8086.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
into the
application and measure performance.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Performance-issues-with-Ignite-L2-cache-compared-to-ehcache-tp8069p8071.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
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.
&g
://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.