How to reduce the memory usage of filebeat

I am using filebeat to collect log files.

I'm using filebeat to collect log files, and on one of my servers, filebeat's memory usage is high.
I would like to limit the memory usage of filebeat.

I have set up queue.mem by referring to the following page, but the situation is the same as before.
(I think the default value was used because it was not mentioned before the configuration)

Why does the memory usage not change?
Also, is there a better way?

vi /etc/filebeat/filebeat.yml

... snip ...

# ======= configuring internal queue =======
queue.mem:
  events: 128
  flush.min_events: 64
  flush.timeout: 5s
top

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 1851 mysql     20   0 6724m 3.8g 6608 S  7.3 48.3  50:59.88 mysqld
 2229 root      20   0 1075m  57m  23m S  2.7  0.7   0:04.29 filebeat

Can you elaborate which memory value you are trying to reduce?

These are the values of VIRT and RES as seen by the top command.
These are currently the second most common values after mysql.

Is it causing issues?
The RES amount is pretty low, and VIRT is managed by the OS, not Filebeat.

Fortunately, we are not experiencing any problems now.

The server was rebooted early in the morning, and it seems that filebeat was temporarily overloaded.

It seems to have settled down now, but exceeding 1G of virtual memory and 60MB of real memory seems to be a bit of a burden on the server, and we are looking for a way to deal with it.

This may be unrelated to the problem, but there seems to be a large number of processes.

ps -efL | grep filebeat | wc -l
12

The number of logs I am sending to logstash with filebeat is four.
Is the number of processes supposed to be this large?

Virtual memory is managed entirely by the OS.

You might be able to minimise its use by tweaking the close_* parameters.

I am decreasing the values of events and flush.min_events in steps and observing the values with the top command, but the values of VIRT and RES are not decreasing.

events is set from 4096 to 2048, 1024, 512, 256, 128
The min_events has been reduced by 6 steps from 2048 to 1024, 512, 256, 128, 64
but there is no change in the values.

Do these operations inherently lower the memory value?

Or should I assume that the memory usage is at a reasonable value and will not go any lower?