THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- This total is dynamic from rebalance to rebalance since the tasks assigned to each thread can change, and hence its the corresponding sub-topology's number of caches can change too.
- That with the triggering Because we have triggering-based caches on top of all RocksDB instance instances for aggregations, we are effectively double caching the records twice (one cache on top of RocksDB, and one cache inside RocksDB as Memtables). We have this extra caching in objects originally only for reducing serialization costs.
...