2.3.x Memory and CPU #4052
Replies: 1 comment
-
Thanks. The cache directory has been fixed in the last docker image. To really get an idea of the benefit of caching on memory consumption, I would suggest to first cache the script using I have to write a full blog post about memory usage. It is a really tricky issue. First off the bat, the discrepancy above could very likely be explained by having disabled Next, you have the issue of shared memory. This is the memory that is used by shared libraries when initiated. The more features you enable, the more shared memory you will consume. Finally, each library has their own initialization routine which also allocates private memory. The more features, the more memory you will allocate, again. Here's a graph of memory usage at startup with each optional dependency enabled on their own: As you can see this varies a lot! Here is the same graph with jemalloc enabled: And, finally on So, for memory consumption, starting with release
|
Beta Was this translation helpful? Give feedback.
-
Summary
I would like to share a comparison of memory and CPU usage between 2.2 and 2.3.
Setup
compose.yml
prometheus.yml
main.liq
Results
My guess is that the spikes in CPU usage are a result of the turbo boost being turned on.
I don't know why liquidsoap 2.3 has 450 MB of managed memory for the first 50 minutes.
Logs
Liquidsoap 2.2
Liquidsoap 2.3
Beta Was this translation helpful? Give feedback.
All reactions