Kimmo L writes:
But i have one small question more about hyperkitty. I have one list, which is quite heavy loaded and contains a lot of data.
I'm not sure what you mean by "heavily loaded" (I guess the HyperKitty processes are using a lot of CPU?) or "a lot of data" (number of posts? MB?) However, 5-10 minutes to "open" the list (what do you mean by "open"? display the top page?) is not acceptable.
Beyond that, it's hard to diagnose with the information you've given, as HyperKitty has a number of options that affect performance. You can help us by doing a little research: searching in the archives for this list and in mailman-developers@python.org for "HyperKitty performance", "HyperKitty slow", and "HyperKitty speed", and doing the same in the HyperKitty issue tracker at https://gitlab.com/mailman/hyperkitty.
Also, some configuration options that are known to affect performance of some HyperKitty operations:
- The search engine. IIRC, Xapian is known to be relativeli fast, Whoosh is relatively slow.
- Configuration of caching (redis).
- Configuration of queues. When you come back with more details, you should provide full configurations for your HyperKitty installation, and tell us what your web stack (webserver, any additional Django middleware) is.
Note: You may post entire configuration files here, but you should redact sensitive information since this list is publicly archived. If you're not sure how to do that, or what is sensitive, you can negotiate sending them directly to one or more of the other developers -- I'm not very useful, I've already told you everything I know because my HyperKitty is small and just works. ;-)
Steve