I agree, we also feel that there's quite some room for performance improvement. After we upgraded to Antelope, it felt like the dashboard responded quite quickly, way faster than we were used to. Now that we upgraded to Caracal, we needed to change the dashboard cache backend to django.core.cache.backends.memcached.PyMemcacheCache as already mentioned, and now it's quite slow again. But I must admit, I'm not the biggest expert in cache modes/configuration etc. But I'd be interested as well if there's a chance to speed things up. Zitat von Kees Meijs <kees@nefos.nl>:
Hi,
That's exactly what we're doing as well. Works fine in terms of availability, although it feels we're missing out with regard to cache, and there's performance that could gain.
On our backlog there's a ticket about a HA (preferably distributed) memcache-replacement (or extension).
Anyone who did this already?
Cheers, Kees
On 13-05-2025 08:22, Eugen Block wrote:
we were facing the same thing when we reinstalled our cloud to be highly available. We had a list of memcached servers for all the required services, and then noticed that a failed control node would disrupt our services. We could pinpoint it to memcached not being highly-available despite having a list of servers. So we decided to point all services to localhost only:
# nova root@controller02:~# grep memcached /etc/nova/nova.conf memcached_servers = localhost:11211
# Dashboard CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.PyMemcacheCache', 'LOCATION': '127.0.0.1:11211', }, }
This has been working great for years now.