You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working through an issue with a single source that's bursting to 100k events/second over 3 minutes, Bazsi chimed in with the suggestion that jemalloc should help reduce fragmentation, particularly in cases where there are lots of workers.
This is the Slack Channel thread where it was discussed (warning, entire thread is 250+ messages, however this was discussed between Bazsi - "I think I got it."
and
Bazsi - "I agree, I just never got around to do it."
While working through an issue with a single source that's bursting to 100k events/second over 3 minutes, Bazsi chimed in with the suggestion that jemalloc should help reduce fragmentation, particularly in cases where there are lots of workers.
This is the Slack Channel thread where it was discussed (warning, entire thread is 250+ messages, however this was discussed between Bazsi - "I think I got it."
and
Bazsi - "I agree, I just never got around to do it."
https://splunk-usergroups.slack.com/archives/CNV918JCQ/p1669837198979099?thread_ts=1668790495.182089&cid=CNV918JCQ
Bazsi quotes
jemalloc is for the rescue.
If we have a high number of workers, the libc allocator does not really scale."
jemalloc-config --libdir
/libjemalloc.so.jemalloc-config --revision
app**- "Sorry I haven't thought about it sooner"
Ryan F quotes/thoughts
The text was updated successfully, but these errors were encountered: