Wez Furlong
e9868287b3
Explicitly spawn via the main tokio runtime when starting the http listener for TSA, so that the tasks spawned by axum are also spawned there. Previously, it would stick to whichever localset thread was used for initializing the lua context, constraining all http request decoding and dispatching to that same thread. With this change in place, in the NOP (stale log record) case I can get 180k qps, this is likely as fast as it will go on this particular machine, as it is 100% CPU bound on all cores. With a current log record I can get 90k qps. In that case, the sqlite performance is the limiting factor and the cores are around 70-80% saturated. For comparison, the rate I get with 2024.11.22-17fafff1 is 27k qps, so this series of commits overall represents a 3.3x improvement in performance. Note that the http server spawning change may also benefit kumod's http injection API. I deliberately left that as it was because it is worth being deliberate about benchmarking that before just shipping the same change--kumod has an http injection pool to explicitly manage performance and care should be taken to evaluate the impact on that.
KumoMTA
KumoMTA is an open-source Message Transfer Agent (MTA) designed for high-performance outbound email functionality, similar to commercial enterprise MTAs such as Momentum, PowerMTA, and Halon.
The KumoMTA project was founded by a group of email industry veterans with decades of experience building and managing high-performance On-Prem MTAs and is supported by a community of some of the largest senders in the world.
Because it is designed for high-performance sending environments, KumoMTA is for experienced email operations professionals who are accustomed to high-performance sending environments and familiar with DevOps practices.
Learn more in our FAQ and at https://kumomta.com/.
Documentation
You can learn more about KumoMTA from the Documentation.
Community
Real-time discussion is available on Our Discord.
Developers
If you are interested in contributing/extending KumoMTA, take a look at DEVELOPERS.md. The #devel channel on Our Discord is for contributors to discuss KumoMTA development.
Reporting Bugs
See How to Report Bugs.
Getting Help
See How to Get Help. For paid support see https://kumomta.com/support.
Getting Updates
You can subscribe to updates at https://kumomta.com/subscribe, we send updates periodically and will never sell nor share your information.
Talk to Us
We're available to talk about the project, book us at https://cal.com/team/kumomta/talk-with-kumomta.