Ah thanks so much for the insights -- we should be in a position to profile
the new library against real data in the next week or so so I'll let you
know how it goes.
On Oct 11, 2016 6:26 PM, "Guozhang Wang" wrote:
> Hello Greg,
>
> I can share some context of KIP-63 here:
>
> 1. Like Eno mentio
Hello Greg,
I can share some context of KIP-63 here:
1. Like Eno mentioned, we believe RocksDB's own mem-table is already
optimizing a large portion of IO access for its write performance, and
adding an extra caching layer on top of that was mainly for saving ser-de
costs (note that you still nee
Thanks Eno -- my understanding is that cache is already enabled to be
100MB per rocksdb so it should be on already, but I'll check. I was
wondering if you could shed some light on the changes between 0.10.0
and 0.10.1 -- in 0.10.0 there was an intermediate cache within
RocksDbStore -- presumably th
Hi Greg,
An alternative would be to set up RocksDB's cache, while keeping the streams
cache to 0. That might give you what you need, especially if you can work with
RocksDb and don't need to change the store.
For example, here is how to set the Block Cache size to 100MB and the Write
Buffer si
Hey Eno, thanks for the suggestion -- understood that my patch is not
something that could be accepted given the API change, I posted it to help
make the discussion concrete and because i needed a workaround. (Likely
we'll maintain this patch internally so we can move forward with the new
version,
Hi Greg,
Thanks for trying 0.10.1. The best option you have for your specific app is to
simply turn off caching by setting the cache size to 0. That should give you
the old behaviour:
streamsConfiguration.put(StreamsConfig.CACHE_MAX_BYTES_BUFFERING_CONFIG, 0L);
Your PR is an alternative, but it
JIRA opened here: https://issues.apache.org/jira/browse/KAFKA-4281
On Sun, Oct 9, 2016 at 2:02 AM, Greg Fodor wrote:
> I went ahead and did some more testing, and it feels to me one option
> for resolving this issue is having a method on KGroupedStream which
> can be used to configure if the oper
I went ahead and did some more testing, and it feels to me one option
for resolving this issue is having a method on KGroupedStream which
can be used to configure if the operations on it (reduce/aggregate)
will forward immediately or not. I did a quick patch and was able to
determine that if the re
