WindmillWWindmill
Powered by
DaanD
Windmill•15mo ago•
2 replies
Daan

Question on worker memory usage

We have configured a worker group in our compose file with a hard limit of 1024M. However, we still see successful flow executions with a peek much larger - is this expected behavior? I suspect this is Docker deciding to not kill the process if it exceeds temporarily the memory limit, but that we should not rely on this behavior being predictable & instead scale up our worker limit to be a safe % above the peak we observe. Is that assumption correct or do we miss something in the way this works?
image.png
WindmillJoin
3,362Members
Resources
Recent Announcements

Similar Threads

Was this page helpful?
Recent Announcements
henri-c

Weekly kenote to tell you about our latest updates https://discord.com/channels/930051556043276338/1278977038430240813 https://youtube.com/live/2dGd9TdT8xs?feature=share

henri-c · 4d ago

Pyra

### HTTP tracing (EE) Capture HTTP requests made by job scripts as observability spans Features: - View HTTP request traces (method, URL, status, timing) in the job details UI - Auto-instrumentation for Native TypeScript, MITM proxy for other languages - Integrates with external OpenTelemetry collectors changelog: https://www.windmill.dev/changelog/http-tracing docs: https://www.windmill.dev/docs/advanced/instance_settings#http-tracing Additionally jobs memory metrics are now fully OSS!

Pyra · 2w ago

henri-c

First keynote of the year here https://discord.com/channels/930051556043276338/1278977038430240813 🙂

henri-c · 4w ago

Similar Threads

Questions about worker memory usage
randako.Rrandako. / help
3y ago
For loops worker usage
JulioJJulio / help
3y ago
Understanding worker memory logs
tl_jacobTtl_jacob / help
8mo ago
Worker on demand
BilgeBBilge / help
16mo ago