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
The Varnish exhausts resources of the VM #3965
Comments
A Varnish instance usually set up to use 8 GB for the stevedore (object store) also need additional memory for the other machinery. |
The usual suspect is jemalloc in combination with Linux transparent huge pages (THP). You might want to have a look at this stackoverflow question. |
bugwash on the first point: We should improve the documentation:
@xiaoyundi on the second point: std.querysort() or vmod_querystring might help you. |
The machine is 4c and 16g. The Varnish allocates 12G memory, which is sufficient for other programs. |
I don't see what we can do to avoid this. |
@xiaoyundi, You allocateed 12G for the regular cache, but Varnish also has the default Transient storage that you can restrict (`varnishd -s Transient=malloc,1G), and memory allocation can be fragmented, plus each thread needs some memory workspace. Here's an old, but hopefully useful article. As to what to do to avoid this:
This ticket doesn't appear to be a bug, which we try to keep github for. Can I invite you to continue this discussion either on the varnish-misc mailing list, IRC, or the discrod server? |
Please leave this ticket open until we improved the documentation. PRs welcome! |
I've had two varnish problems recently,
(edit: removed duplicates, no other details were given)
The text was updated successfully, but these errors were encountered: