-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
db_bench: align the tests we're using #325
Comments
also fix BGWriter, readrandom, seekrandom and readrandomwriterandom.
|
make sure all the tests used: 1. are working on all cfs if theres more than 1 2. use one rand num to get the db and cf and the key which makes it possible to find a key in a cf later on. 3. have the ability for read and write limiter wherever relevant. tests: seekrandomwriterandom, BGWriter, readrandom, seekrandom and readrandomwriterandom
@erez-speedb , plz run performance. we're expecting no change in all tests. the only change that should be visible is in the seekrandomwriterandom which will use all the cfs in huge db test and the seekradomwhilewriting now writes to all cfs |
@erez-speedb , status? |
@Yuval-Ariel The multi CF is running but I'm not sure what performance is there to test here? |
its a matter of correctness.. but if theres a performance difference in the single cf tests then its bad |
Multi CF test, |
@Yuval-Ariel I tested few times and both large obj and small DB tests shows the degradation This is unless the degradation is from introducing the rate limit, and then it is part of a separate discussion. |
make sure all the tests used: 1. are working on all cfs if theres more than 1 2. use one rand num to get the db and cf and the key which makes it possible to find a key in a cf later on. 3. have the ability for read and write limiter wherever relevant. tests: seekrandomwriterandom, BGWriter, readrandom, seekrandom and readrandomwriterandom
make sure all the tests used: 1. are working on all cfs if theres more than 1 2. use one rand num to get the db and cf and the key which makes it possible to find a key in a cf later on. 3. have the ability for read and write limiter wherever relevant. tests: seekrandomwriterandom, BGWriter, readrandom, seekrandom and readrandomwriterandom
make sure all the tests used: 1. are working on all cfs if theres more than 1 2. use one rand num to get the db and cf and the key which makes it possible to find a key in a cf later on. 3. have the ability for read and write limiter wherever relevant. tests: seekrandomwriterandom, BGWriter, readrandom, seekrandom and readrandomwriterandom
make sure all the tests used: 1. are working on all cfs if theres more than 1 2. use one rand num to get the db and cf and the key which makes it possible to find a key in a cf later on. 3. have the ability for read and write limiter wherever relevant. tests: seekrandomwriterandom, BGWriter, readrandom, seekrandom and readrandomwriterandom
make sure all the tests used: 1. are working on all cfs if theres more than 1 2. use one rand num to get the db and cf and the key which makes it possible to find a key in a cf later on. 3. have the ability for read and write limiter wherever relevant. tests: seekrandomwriterandom, BGWriter, readrandom, seekrandom and readrandomwriterandom
make sure all the tests used: 1. are working on all cfs if theres more than 1 2. use one rand num to get the db and cf and the key which makes it possible to find a key in a cf later on. 3. have the ability for read and write limiter wherever relevant. tests: seekrandomwriterandom, BGWriter, readrandom, seekrandom and readrandomwriterandom
make sure all the tests used: 1. are working on all cfs if theres more than 1 2. use one rand num to get the db and cf and the key which makes it possible to find a key in a cf later on. 3. have the ability for read and write limiter wherever relevant. tests: seekrandomwriterandom, BGWriter, readrandom, seekrandom and readrandomwriterandom
Describe the bug
when used with multiple cfs, the test will only use the default cf.
Additional context
this has been addressed before but must've slipped during rebasing
The text was updated successfully, but these errors were encountered: