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

Memcached high CPU load without usage #5691

Closed
markuszeller opened this issue Jul 31, 2020 · 5 comments
Closed

Memcached high CPU load without usage #5691

markuszeller opened this issue Jul 31, 2020 · 5 comments

Comments

@markuszeller
Copy link

markuszeller commented Jul 31, 2020

Installed memcached via sudo apt install libmemcached-dev .

Launching it with sudo service memcached start instantly consumes high CPU load without anything else beeing done. Using it in PHP for example works fine, but the CPU load keeps high until service is stopped.

memcached

Microsoft Windows [Version 10.0.19041.388]
Ubuntu 20.4 from Store

C:\WINDOWS\system32>wsl -l -v
NAME STATE VERSION

  • Ubuntu Stopped 1

Looking with htop in WSL itself, the CPU usage of the memcached is 0. RAM about 400 MB.

@onomatopellan
Copy link

19041
Ubuntu 20.4 WSL1

It's not recommended to use Ubuntu 20.04 WSL1 in build 19041 or you will hit #4898.
You need to convert Ubuntu distro to WSL2, use one of the available workarounds or wait for the fix to come via Windows Update..

@markuszeller
Copy link
Author

markuszeller commented Jul 31, 2020

The problem is, that WSL2 does not work with VirtualBox, so I need to use WSL1. I have no issues at all, only the high CPU load. So I am starting the service only when needed.

@onomatopellan
Copy link

onomatopellan commented Jul 31, 2020

That's because libc6 and thus sleep are broken in Ubuntu 20.04 WSL1 build 19041.
Try this workaround:
#5125 (comment)

@therealkenc
Copy link
Collaborator

Confirmed just to be sure that was it

image

/dupe #4898

@ghost
Copy link

ghost commented Jul 31, 2020

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

@ghost ghost added the duplicate label Jul 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants