-
Notifications
You must be signed in to change notification settings - Fork 216
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
autokill if inactive since some time + memory becomes low? #364
Comments
I think we already have a quite complex strategy in place: |
Your exact use case could be covered by the |
It does, indeed. The tool I've used for similar tasks before is https://github.com/oshi/oshi. The downside is that it's a 800kB library, so perhaps a less heavy (but more brittle) way would be to call an OS-specific command. Linux and Unix have |
sigar library would work as well and is quite easy to setup (as you know ;)) |
If it's only a couple of native functions, they could be added to jansi. |
Depends on #400 |
Add an expiration strategy if the system has less than 5% memory available, fixes #364
Hi,
It is common to let mvnd "leak" (it is designed for that right? ;)) but when working on other builds which take a lot of memory using mvn and not mvnd it can eat too much memory (typically the case running graal native-image in the build) - in my case mvnd was eating something around 3G.
I wonder if a condition/scheduled task to kill the daemon if inactive since some minimum time (10mn?) and memory becomes too low (85% or so of the system?) would be beneficial?
Hope it makes sense.
Romain
The text was updated successfully, but these errors were encountered: