mirrors/dragonfly
1
0
Fork 0
mirror of https://github.com/dragonflydb/dragonfly.git synced 2025-05-10 18:05:44 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

Move assets to static (#247)

Browse source 
Signed-off-by: Oded Poncz <oded@poncz.com>

Signed-off-by: Oded Poncz <oded@poncz.com>
This commit is contained in:
odedponcz 2022-08-18 22:55:12 +03:00 • committed by GitHub
parent 3d3d395e25
commit 08cda413f7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -20,7 +20,7 @@ Dragonfly's core properties make it a cost-effective, high-performing, and easy-
## Benchmarks ## Benchmarks
<img src="http://assets.dragonflydb.io/repo-assets/aws-throughput.svg" width="80%" border="0"/> <img src="http://static.dragonflydb.io/repo-assets/aws-throughput.svg" width="80%" border="0"/>
Dragonfly is crossing 3.8M QPS on c6gn.16xlarge reaching x25 increase in throughput compared to Redis. Dragonfly is crossing 3.8M QPS on c6gn.16xlarge reaching x25 increase in throughput compared to Redis.
@ -71,7 +71,7 @@ In the following test, we filled Dragonfly and Redis with ~5GB of data
using `debug populate 5000000 key 1024` command. Then we started sending the update traffic with `memtier` and kicked off the snapshotting with the using `debug populate 5000000 key 1024` command. Then we started sending the update traffic with `memtier` and kicked off the snapshotting with the
"bgsave" command. The following figure demonstrates clearly how both servers behave in terms of memory efficiency. "bgsave" command. The following figure demonstrates clearly how both servers behave in terms of memory efficiency.
<img src="http://assets.dragonflydb.io/repo-assets/bgsave-memusage.svg" width="70%" border="0"/> <img src="http://static.dragonflydb.io/repo-assets/bgsave-memusage.svg" width="70%" border="0"/>
Dragonfly was 30% more memory efficient than Redis at the idle state. Dragonfly was 30% more memory efficient than Redis at the idle state.
It also did not show any visible memory increase during the snapshot phase. It also did not show any visible memory increase during the snapshot phase.

4
docs/memcached_benchmark.md
View file

@ -1,8 +1,8 @@
Contention in memcached under the high write throughput. Contention in memcached under the high write throughput.
<img src="http://assets.dragonflydb.io/repo-assets/memcached_perf_top.png" width="100%" border="0"/> <img src="http://static.dragonflydb.io/repo-assets/memcached_perf_top.png" width="100%" border="0"/>
Overall CPU usage of memcached when performing SETS benchmark: Overall CPU usage of memcached when performing SETS benchmark:
<img src="http://assets.dragonflydb.io/repo-assets/memcached_cpu_usage.png" width="100%" border="0"/> <img src="http://static.dragonflydb.io/repo-assets/memcached_cpu_usage.png" width="100%" border="0"/>