gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update benchmarking notes.

Browse Source 
Former-commit-id: bae2409cceb26124a346a7e8db40b183952e31f8
This commit is contained in:
JohnSully 2019-02-26 02:30:03 -05:00 committed by GitHub
parent f474419764
commit f1b8f76167
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -17,8 +17,12 @@ Benchmarking KeyDB
Please note keydb-benchmark and redis-benchmark are currently single threaded and too slow to properly benchmark KeyDB. We recommend using a redis cluster benchmark tool such as [memtier](https://github.com/RedisLabs/memtier_benchmark). Please ensure your machine has enough cores for both KeyDB and memteir if testing locally. KeyDB expects exclusive use of any cores assigned to it.
If you find a scenario where performance is not as expected please open an Issue, we take performance extremely seriously.
We do most of our benchmarks on AWS m5.metal boxes with the following command
./memtier_benchmark --key-pattern=S:S --ratio=3:2
KeyDB is currently very sensitive to core affinity and the CPU your network interrupts arrive on. This should improve over time as we gain flexibility on which cores clients can execute on.
New Configuration Options
-------------------------