mirror of
https://github.com/mailscope/kumomta.git
synced 2026-09-10 04:22:13 +00:00
Wez Furlong
5a53af04a5
The flume bounded queue doesn't eagerly allocate its full capacity and otherwise runs fast enough for our logging that we don't notice the difference. This reduces the "static" footprint of kumomta in the (hopefully) common case where logging is keeping up with the system throughput and is not approaching the limit of the default logging backlog. Remove unused reference to async-channel from kumo-server-runtime.