On 5/28/25 08:27, roughnecks via Mailman-users wrote:
It's the manage.py qcluster whatever is called. I have shut down MM for the time being, because I'm not fully motivated to have it running, so I can't be more accurate right now.
I don't know how qcluster is configured in the Debian packages (which are out of date and possibly buggy anyway). You may be using django-q <https://django-q.readthedocs.io/en/latest/> and if so, you should migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both typically use memcached as a backend.
Settings that control this are typically
# Set retry > timeout.
Q_CLUSTER = {
'timeout': 300,
'retry': 360,
'save_limit': 100,
'orm': 'default',
}
and possibly a setting like 'workers': 2, (default is the CPU count of
the system but see
<https://django-q2.readthedocs.io/en/master/configure.html#f1>).
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache',
'LOCATION': '127.0.0.1:11211',
}
}
although the default if not set is
CACHES = {
"default": {
"BACKEND": "django.core.cache.backends.locmem.LocMemCache",
}
}
It is the 'orm': 'default' setting that says to use Django's CACHES.
See <https://django-q2.readthedocs.io/en/master/brokers.html#django-orm>.
You can get info about what qcluster is doing with manage.py qinfo and
monitor things with manage.py qmemory and manage.py qmonitor.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan