top
command first. You need to identify which part of your system is the bottleneck (CPU? Memory? Disk I/O? etc).num_threads
option will parallelize your outputs (the default is 1). Using multiple threads can hide the IO/network latency. This parameter is available for all output plugins.num_threads
option as well.RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR
to lower value. RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR
is used for full GC trigger and the default is 2.0
. Quote from documentation.2.0 * before old objects
. This improves the throughput but it grows the total memory usage. This setting is not good for low resource environment, e.g. small container. For such cases, try RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=0.9
or RUBY_GC_HEAP_OLDOBJECT_LIMIT_FACTOR=1.2
.in_multiprocess
plugin.