-
Notifications
You must be signed in to change notification settings - Fork 33
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
Why does SET operation have slower performance than GET on redis-benchmark? #15
Comments
Hi, |
PMEM_IS_PMEM_FORCE is one of the options, more like a temporary workaround. |
@jschmieg I tried to set PMEM_IS_PMEM=1 when running redis-server. But I found new error when running redis-benchmark. I ran benchmark command like this.
then, redis-server was shutted down with this error logs.
command without random key @Maciuch My kernel version is "CentOS 7 (4.15.0)" now. How can I set MAP_SYNC flag for this kernel? And, Is this flag option force to use clflush instead of msync syscalls? |
Could you please verify that:
|
MAP_SYNC will be used by default by PMDK when available. Therefore no need to do anything from an application perspective, you can already now switch to a pull request branch from PMDK if you wish to test it, or wait a bit longer. Cheers, |
@jschmieg I figured out that @Maciuch Thank you for detail explanation 👍 |
Back port memKeyDB to redis v3.2.12
I configured emulation version of pmem referring official blog.
link
And than, build & configure pmem/redis to use pmem.
...and run redis-server by this command.
then, server is executed well like this.
I execute redis-benchmark for pmem/redis. Then I could see that SET operation has worse performance than GET operation.
evaluated time to complete 100000 SET operation: 16.72 sec
evaluated time to complete 100000 GET operation: 0.63 sec
This is result of redis-benchmark on pmem/redis without using pmem.
evaluated time to complete 100000 SET operation: 0.63 sec
evaluated time to complete 100000 GET operation: 0.63 sec
Without pmem, benchmark show that evaluated time to operation is same both GET and SET.
I just wonder why SET has worse performance than GET on pmem.
Is there any additional configuration for pmem/redis? (ex. CPU setup, cache setup, ...)
The text was updated successfully, but these errors were encountered: