When activating enable speedb features in db_bench, we are creating and overriding Options' properties.
db_bench has its own.
For example, db_bench has its own cache handling that seems not to be fully synchronised with the SharedOptions's own cache entity:
no_block_cache is set according to the dbbench's cache member.
db_bench creates a SimCache as its cache if simcache_size >= 0.
We should review all the overrides that enables speedb features does and make sure they are fully synchronized with db_bench.
@erez-speedb moved to performance in order to check if it doesn't fail for the performance tests, it doesn't affect the performance of the tool or the db itself.
When activating enable speedb features in db_bench, we are creating and overriding Options' properties. db_bench has its own. For example, db_bench has its own cache handling that seems not to be fully synchronised with the SharedOptions's own cache entity:
We should review all the overrides that enables speedb features does and make sure they are fully synchronized with db_bench.