GC Activity
Open
enhancement
performance improvements
- Dominant language
- Java
- Stars
- 14.9k
- Forks
- 3.5k
- Avg merge
- 19h 14m
- Merged PRs (30d)
- 63
Description
It would be nice if Logstash would create a Pool of reusable Event objects instead of constantly creating new ones.
The purpose of this, is to reduce the GC Overhead when running a Pipeline.
I recommend that if this goes forward, the Pool size should be equal to the Max In Flight objects in the Pipeline.
It would cost a bit of memory, but it will boost the performance.
Log4J2 has already done something similar. See [here](https://www.infoq.com/news/2016/05/log4j-garbage-free).
Currently from my benchmarks with VisualVM, i find Logstash very GC-Active since it disposes a lot of objects.
Contributor guide
Assessment
This issue has not been assessed yet.