Replies: 2 comments 3 replies
-
I ran a fluent-bit with jemalloc on a VM and consumes ~85MB. Then reboot machine, run exactly the same configuration on the same machine and now it consumes ~220MB. Why is this happening? is this related with system free memory? |
Beta Was this translation helpful? Give feedback.
3 replies
-
I also have a similar problem about memory, my fluent-bit is enabled jemalloc, I found that when fluent-bit processes logs, the memory usage will gradually increase, and when the traffic stops, I will find that the memory is not released immediately, is this part normal? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm building fluent-bit using documented instructions. I noticed that despite use of jemalloc is strongly suggested, on the Makefile it's disabled:
https://github.com/fluent/fluent-bit/blob/master/CMakeLists.txt#L114
On the binary provided by the debian/ubuntu repository it's actually enabled (FLB_HAVE_JEMALLOC flag is present):
Other important builds had jemalloc enabled:
https://github.com/aws/aws-for-fluent-bit/blob/develop/scripts/dockerfiles/Dockerfile.main-release#L7
Another popular log managers discard jemalloc years ago giving their reasons:
https://vector.dev/highlights/2021-06-02-drop-jemalloc/
So I'm confused about this configuration. I mainly work with linux machines and use 'tail' inputs, so I'm not really sure about use jemalloc or default memory allocator. Principal reason is that jemalloc builds sometimes uses as twice the ram of the default memory allocator. Can anyone offer some guide?
Beta Was this translation helpful? Give feedback.
All reactions