Univention Bugzilla – Bug 31329
Performance guide and group cache
Last modified: 2024-04-17 13:16:18 CEST
Currently the performance guide recommends to disable the cache invalidation on changes. The check is done every 15 minutes. Which way better is depends on the interval of group changes. If changes on group memberships are mostly done at night, it is better to use the cache invalidation on changes or it might be a good idea to re-create the cache in a real large environment only once a day. For that nss/group/cachefile/invalidate_interval should be introduced. If the generation is a problem and a lot of servers are used, it might be better to enable the cache generation only on one system and distribute the cache file via ssh / sftp. The performance guide should introduce all variables and some examples should be explained.
See https://gorm.knut.univention.de/otrs/index.pl?Action=AgentTicketZoom&TicketID=545623&ArticleID=1284101&ZoomExpand=0#1284101 for an customer example.
This bug hasn't seen any update for several years. I close it. If you still see a need for it, you can reopen the bug. Please add an argumentation about why it's important to take care of it.