On Mon, Dec 3, 2018, at 12:04 PM, Stefan Tatschner wrote:
On Mon, 2018-12-03 at 11:56 -0800, Abhilash Raj
The ORM backend in DjangoQ exists for low
performance workloads where
you can afford to poll the database that frequently and not have
negative affects on rest of your system. It also lets you avoid
installing a message broker like Redis.
If your system does handle a ton of traffic, then it is recommended
to use Redis or similar higher-performant systems.
My system does handle very low traffic (at max 10 mails per day). I
noticed the database polls, since after migrating from mailman2 to
mailman3 my VPN traffic between the web frontend and the database
server increased like crazy.
This architecture might scale wonderfully for large and distributed
systems, but it is questionable for low traffic sites. Maintaining
multiple databases (or call it broker) for a few small mailing lists is
just too much.
And I agree to that :)
As the current system relies on polling and cron to run some routine tasks,
it is quite in-efficient when it comes to low-usage systems. We can fix that with
a more event-based system, and that is on my things to change in Hyperkitty.
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
Abhilash Raj (maxking)