yuvala

Sure i can do that. Im just worried that this new parameter will be too confusing since it means "flush will wait for some stall conditions to clear if there...

currently disabling the test DynamicLevelCompressionPerLevel in db/db_test.cc to be able to merge https://github.com/speedb-io/speedb/pull/423 . reenable the test with the PR to fix this issue

for the IsDone assertion failure, my findings are: When the stress test resumes and finds a trace file and state file with a seq number prefix e.g. 0.state , The...

the problem doesnt happen in the small_obj test with hashspd memtable but it does with skip list.. attaching LOGs - [LOG-overwrite_hashspd.gz](https://github.com/speedb-io/speedb/files/11756864/LOG-overwrite_hashspd.gz) [LOG-overwrite_skiplist.gz](https://github.com/speedb-io/speedb/files/11756870/LOG-overwrite_skiplist.gz) @ayulas any thoughts?

@udi-speedb 1. The goal here is to prevent compactions running at db close when the flush is waiting for stall conditions. So that close is as fast as possible and...

what do you think @udi-speedb ?

1. options->env->GetBackgroundThreads(Priority pri) (e.g in env/env_posix.cc) 2. its per Env and the env applies to all dbs which have been given that env. so all the dbs using the same...

what happens when a user sets WBM.max_flushes = 4, but the env thread pool for these dbs only supports max 3 flush threads?

i agree this should be done as part of a bigger project of correctly setting and sanitizing options for multi-db setup

and perhaps a note in the documentation of this feature explaining to the user how to set the WBM.max_flushes and its connection to the env's max flush threads.