Well, that was a new design assumption for the architecture of our PoC.
At the beginning, we wanted some "multi-tenant" caches with 1 continuous
query for each. Then, we've tried to switch with one cache and 1 continous
query for each key.
But, you're right. We have already started to challenge our
Well, actually we were interesting in having continuous queries listening
multi-tenant caches.
This was the postulate for the architecture of a PoC project. Based on this
discussion, we are switching to another architecture postulate where we have
one cache with thousands continuous queries listen
Thanks a lot for the answer!
We'll try to run tests with these hints.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Lots-of-cache-creation-become-slow-tp11875p11906.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
We are trying for test purposes to create lots of cache on a machine.
Something like:
for (int i = 0; i < 1; i++) {
IgniteCache cache;
cache = ignite.getOrCreateCache("cache-" +
i).withAsync();
LOGGER.info("starting to read cache #" + cache.getName());
}
What we are noti
Thanks for the reply and answering all of our questions!
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Can-a-Continuous-Queries-miss-some-updates-order-tp11620p11623.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ueries can be
created? Does Apache Ignite support hundred thousands of creation of caches
and continuous queries?
The code for the tests can be found there:
https://github.com/ctranxuan/ignite-cq-bench-parent
We use Ignite 1.9.0.
Thanks in advance for the answers!
--
View this message in cont
