Has GC_INTERVAL gone missing?
See original GitHub issueThumbor request URL
n/a
Expected behaviour
A config parameter GC_INTERVAL
is listed in Thumbor’s documentation here. It was added from this PR back in 2017. I’ve been attempting to use this while troubleshooting high memory usage on our Thumbor pods.
Actual behaviour
But the code in thumbor/server.py
to implement timed garbage collection has since disappeared, and grepping the codebase for any use of GC_INTERVAL
returns no matches. Is GC_INTERVAL
still supported?
Operating system
n/a
Your thumbor.conf
n/a
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Why are Full GCs not running on my gcInterval I set?
I am trying to figure Full GCs to run every 10 minutes. I have used the gcInterval JVM arg in the past on...
Read more >Improving Stability in Low Memory Situations - IBM
When our clients that were experiencing out of memory errors enabled these parameters, the memory issues disappeared. So, if you can see from...
Read more >Help! Jboss won't start| JBoss.org Content Archive (Read Only)
Hello, I have a problem: when I launch run.bat, it stops at this string: rem ... gcInterval=3600000 -Djava.endorsed.dirs="D:\jboss-4.2.3.
Read more >how to solve this error? - Oracle Communities
Hi ALL, when i try to run my JBOSS 4.0 in ubuntu it shows the following error run.sh: Missing file: /lib/tools.jar run.sh: Unexpected ......
Read more >gist:312494 · GitHub
gcInterval =3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net. ... It has been detected that the cluster admin user and password have not been ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can’t speak for everyone but my use case is deploying it to a Kubernetes cluster alongside the rest of our application stack, and I imagine that’ll be a fairly common one. Best practice is to give pods a fixed memory limit so while we aren’t very resource-constrained we do need predictable usage.
As @kkopachev noted the usage for us has stabilised around 1GB per Thumbor instance. That’s a lot higher than before but we can live with it. I had hoped the
GC_INTERVAL
setting would help us reduce it by triggering garbage collection differently.Given
GC_INTERVAL
no longer does anything I think a simple solution would be to remove it from the documentation. Lower memory usage is always welcome though!This issue was closed because it has been stale for 5 days with no activity.