-
Notifications
You must be signed in to change notification settings - Fork 22
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
Investigate Increased Memory Usage #17
Comments
Nice! Those are both really good pieces of information! If you feel up to it, I'd happily merge a PR that changes that line to a debug level message (no pressure, I can get to it later today). Yes, for the time being we should probably bump the memory requested by the plugin in the default manifest included in the repository. In the medium term we should try to look at why memory usage has increased. I'll do some memory profiling to see if we can get it back down. Thanks again @dejanzelic |
Sweet! I'll submit a pr for the log level thing when I'm in front of my computer. |
Hello, Not sure if this related, but I seem to be encountering a memory leak where Generic Device process is killed due to "Memory cgroup out of memory" (see dmesg log below). I'm currently running Kubernetes 1.27 with the latest release of your 'generic-device-plugin' as of today. Running on RaspberryPi4B 8gb clusters. Ubuntu Server 22.04 LTS
|
xref: #45 |
Hola!
Thanks for making this, it's super useful!
I'm running this on a 4 cluster node (3x 2GB Pi 4b, and 1x 8GB Pi 4b) to expose the sound device and USB device. I was having a weird issue where everything works great for 2 of my nodes and the I could only get it to work with the other 2 nodes once (with the default DaemonSet config). The 2 nodes that didn't work would never show any logs.
The issue started when I was trying to use the new USB device feature. But even when I would go back to the default, I still had the same issue.
I read the issue here: #11 And decided to try also upping the memory limit. As soon as I did that everything worked!
So it does sound like the new build uses more memory. Here is my current config that's working:
While I'm here, I figured I should give some additional feedback. On the nodes without the USB device, I get this log message constently:
It's not a problem, but I don't think this should be a "info" level message.
The text was updated successfully, but these errors were encountered: