Hi Quan.
Here documentation and commands i used
https://github.com/prosgarz35/james-fast/blob/main/README.md
And here is what i used for testing
https://github.com/prosgarz35/james-fast/tree/main/tools
SmtpHighLoadBenchmark.class and SmtpHighLoadBenchmark.java
Yeah i used AI for develop this, but i test all stability up too 900k
mails to 1 mailbox and trying sigkill and other dirty stuff to test how
james, s3, postres, artemis handle it. And nothing bad happed.
С уважением,
Руководитель ИТ
ООО «КПС-Технологии»
Терсков Илья Андреевич
Моб.: +7 (996) 415-16-29
E-mail:[email protected]
УВЕДОМЛЕНИЕ О КОНФИДЕНЦИАЛЬНОСТИ:
Это электронное сообщение и любые документы, приложенные к нему,
содержат
конфиденциальную информацию. Настоящим уведомляем Вас, что если это
сообщение
не предназначено Вам, использование, копирование и распространение
информации,
содержащейся в настоящем сообщении, а также осуществление любых действий
на
основе этой информации строго запрещено. Если Вы получили это сообщение
по
ошибке, пожалуйста, сообщите об этом отправителю по электронной почте и
удалите данное сообщение.
CONFIDENTIALITY NOTICE:
This email and any files attached to it are confidential. If you are not
the
intended recipient, you are notified that using, copying, distributing,
or taking
any action in reliance on the contents of this information is strictly
prohibited.
If you have received this email in error, please notify the sender and
delete this
message.
------ Исходное сообщение ------
От "Quan tran hong" <[email protected]>
Кому "James Users List" <[email protected]>
Дата 22.09.2026 10:39:21
Тема Re: James Artemis
Hi Terskov,
Thank you very much for triaging James and optimizing its performance!
Offloading blobs to S3 Silo (a MinIO fork).
Yes. Relying on Postgres for blobs (especially big blobs) is not as good as
proper object storage.
We developed the Postgres app so it could work either in standalone mode
(for people who just need simplicity in deployment), or in a distributed
mode (can work with RabbitMQ, OpenSearch, S3 object storage) for better
performance and scalability.
I’ve shared the code and documentation in the following repositories:
Your benchmark and the way you optimized James' Postgres performance are
very interesting!
Is it possible to record this somehow more formally, to share the
experience with the James community better? Either in the james-project
Antora documentation or an article/post?
Thank you a lot again for using James!
Regards,
Quan
On Tue, Sep 22, 2026 at 10:29 AM Терсков Илья Андреевич <[email protected]>
wrote:
Hi everyone,
I've been closely following the project's development and saw the recent
update from Benoit Tellier, which improved performance and reduced
latencies in the postgres-app version by about 40%. Great work, but in
my testing, the throughput still hit a ceiling at around 400 messages
per second. Furthermore, running basic James entirely on PostgreSQL 17
resulted in only around 25–30 messages per second.
Through some architectural adjustments, I managed to push throughput
past 2,000 messages per second. The key changes:
1. Migrating to Apache ActiveMQ Artemis. In my experience, Artemis was
the main differentiator thanks to its asynchronous architecture, whereas
classic ActiveMQ seemed capped at around 400 msg/s even with tuning.
2. Offloading blobs to S3 Silo (a MinIO fork).
3. Several minor tweaks and optimizations across the setup.
All tests were run on the following hardware:
• CPU: Intel Core i5-9500
• RAM: 24 GB DDR4
• Storage: Samsung 860 EVO SSD
I’ve shared the code and documentation in the following repositories:
• Integration with Artemis:
https://github.com/prosgarz35/james-project-fast
• Ready-to-test standalone bundle (built for Windows):
https://github.com/prosgarz35/james-fast
I'm really glad to see James actively evolving and hope these findings
and repositories prove helpful to the team. Any feedback is welcome!
С уважением,
Руководитель ИТ
ООО «КПС-Технологии»
Терсков Илья Андреевич
Моб.: +7 (996) 415-16-29 <+7%20996%20415-16-29>
E-mail:[email protected]
УВЕДОМЛЕНИЕ О КОНФИДЕНЦИАЛЬНОСТИ:
Это электронное сообщение и любые документы, приложенные к нему,
содержат
конфиденциальную информацию. Настоящим уведомляем Вас, что если это
сообщение
не предназначено Вам, использование, копирование и распространение
информации,
содержащейся в настоящем сообщении, а также осуществление любых действий
на
основе этой информации строго запрещено. Если Вы получили это сообщение
по
ошибке, пожалуйста, сообщите об этом отправителю по электронной почте и
удалите данное сообщение.
CONFIDENTIALITY NOTICE:
This email and any files attached to it are confidential. If you are not
the
intended recipient, you are notified that using, copying, distributing,
or taking
any action in reliance on the contents of this information is strictly
prohibited.
If you have received this email in error, please notify the sender and
delete this
message.
