[Pkg-mailman-hackers] Bug#914099: Bug#914099: mailman3-full: mailman3-web-qcluster causes high database load

[Jonas Meurer]

Hi Stefan,

Stefan Tatschner:
> On Mon, 2018-11-19 at 13:09 +0100, Stefan Tatschner wrote:
>> I installed the mailman3-full package from the buster repository. The
>> qcluster component generates a high database load with these queries:
> 
> The reason for this is that the django qcluster component polls the
> database regularly:
> 
> https://github.com/Koed00/django-q/issues/139
> https://django-q.readthedocs.io/en/latest/configure.html#poll
> 
> IMO it would make sense to make the qcluster component optional, since
> there are cronjobs anyway. But that's an upstream issue...
> 
> In the meanwhile debian could configure a lower default poll rate. I
> have set 5 seconds instead of the default 0.2 in order to reduce
> database traffic.
> 
> Oh and the issue is related to hyperkitty, which is part of the
> mailman3-full metapackage. Maybe someone could tag this issue
> accordingly.

Thanks a lot for bugreport and follow-ups. We decided to patch
settings.py in mailman3-web package and lower the polling interval for
django-q cluster to 5 seconds, as you suggested.

This change will be shipped with the next upload of mailman-suite.

Cheers
 jonas


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/attachments/20190123/320838a3/attachment-0001.sig>