Closed arnaudsj closed 9 years ago
Thanks! some notes about the benchmarking: by default redis benchmark measures all of the commands most of which are not supported by Serenity. They should pass, but server return errors.
It is better to exactly specify supported commands, like: ./redis-benchmark -t set,get -n 1000000. Or use memtier_benchmark.
Thank you, that makes sense. I guess the server should not crash though when issued those commands no, but instead return an error no? I will retest with just set & get.
Yes, it critical not to crash in any such case. Also i would like to note, even if a crash happens - data is safe due to storage engine guarantees.
Hi,
I found an issue when attempting to run the benchmark against a freshly built serenity binary on Ubuntu 14.04 LTS.
I run the redis-benchmark as follow (I could not run it with -k 1, getting "server closed connection":
And eventually it crashes the serenity process:
FYI, I am using the following Dockerfile to build serenity and run it: