Skip to content
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

Performance issues #2

Open
webdobe opened this issue May 9, 2018 · 3 comments
Open

Performance issues #2

webdobe opened this issue May 9, 2018 · 3 comments

Comments

@webdobe
Copy link

webdobe commented May 9, 2018

I am running Redis in global mode for a swarm setup and have some performance issues.

I am looking at the logs and I have this going on as well, which may or not be related:

1:M 24 Apr 22:03:10.486 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.,
1:M 24 Apr 22:03:10.486 # Server started, Redis version 3.2.8,
1:M 24 Apr 22:03:10.486 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.,
1:M 24 Apr 22:03:10.486 * The server is now ready to accept connections on port 6379,
1:M 24 Apr 22:03:10.486 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.

Any thoughts?

@csandanov
Copy link
Member

Have you tried following the instructions? None of these can be done from the image

@webdobe
Copy link
Author

webdobe commented May 11, 2018

Yeah it says that it is a read only filesystem.

@webdobe
Copy link
Author

webdobe commented May 11, 2018

I am noticing there are performance issues and limitations because I can only use this redis setup in the swarm in global mode (which is super slow). It would be nicer if we could replicate this across the swarm in cluster mode so that each container is updated. Currently if I don't run it in global. Cache is different in each node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants