udi-speedb
udi-speedb
@hilikspdb - It seems there is no dedicated cache entry role for compression dictionaries. There is: ``` // Compression dictionary building buffer's charge to account for // its memory usage...
> you can add this ... currently the "metadata block" (which contains the delete range tombstone) and the dictionary are accounted as "others" > […](#) > On Wed, Oct 11,...
The motivation is to have a report per benchmark, and to allow easy association of the generated report with its benchmark. In addition, once [https://github.com/speedb-io/speedb/issues/220](url) is supported, there may be...
To sum this up: Compression Dictionary blocks will remain under the kOtherBlock cache entry role and will be reported under that role.
@ofriedma, @speedbmike - Please review
> Is this issue up for grabs? Hi, Yes it is. Thanks.
@giladmaya - BTW, we will be happy to assist if you have any questions about this issue (and in general), or in case you would like to discuss, etc. Please...
@giladmaya: That makes sense. You may also look at `--column_family_distribution` or (our new) `--dbs_to_use` flag, coming in this release as a db_bench enhancement (https://github.com/speedb-io/speedb/issues/220) A few issues that I think...
> @udi-speedb: `--column_family_distribution` and `--dbs_to_use` are quite similar to my suggestion, will take a look at their implementation to see if there's anything I can reuse. > > * I...
@giladmaya - Hi, are you planning to work on this issue?