Hi together, i justed wanted to ask about the memory management of kumomta. my maschine has 64 gb ram and sometimes its getting very close to the max available memory (63 GB) and then kumomta don’t accept any message anymore. currently we have around 15k messages in the queue. the spool and meta is done with RocksDB.
btw i added your recommended performance settings: https://docs.kumomta.com/userguide/operation/performance/
the problems started kinda as i added dkim signing. before it was done by our application
That memory seems rather high for only 15k messages, but rejecting as the ram gets full is the designed behavior.
How large are your individual messages?
What version are you running? How many queues do you have? What are your traffic patterns like? What’s in your configuration?
(As in all the things from the READ ME FIRST)
kumo version: kumod 2024.06.10-84e84b89
disti:
Linux mta02 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux
queue.toml (875 Bytes)
init.lua (7.15 KB)
i only have the default queue
i have 50 sending IPs
all assigned to pool 1
the avg. message size so 1.5 kb
but somethings we have attachments
so then it grows
we deliver up so 400 messages / s into kumo
we deliver them by smtp and sent multiple messages per connection
we have 3725 dkim keys for individual domains
shaping.toml (14.4 KB)