You are not logged in.
Pages: 1
Hello, I’m currently performing some performance analysis and optimizations on the GLPI instance at my company and would like to know if there's anything else I can test or modify.
GLPI Version: 10.0.11
Query time when searching all open tickets (40,900):
Debug mode information:
Initial Execution Time: 9306 ms
Total Execution Time: 30848 ms
Memory Usage: 5.94 MiB / 512 MiB
Memory Peak: 27.07 MiB
2143 database requests
26 requests
Time to First Paint: 3953 ms
Total Resources Size: 13.62 MiB
Configurations:
Redis:
session.save_handler = redis
session.save_path = "tcp://myredis:6379/0"
redis.session.locking_enabled = 1
redis.session.lock_retries = 10000
session.gc_maxlifetime = 30600
cache.php: 'dsn' => 'redis://myredis:6379/2'
I’ve changed the innodb_buffer_pool_size to 1G in the server.cnf and observed improvements in some queries.
Some performance improvements I found include using Zend Opcache and Redis. However, I'm not sure if using Zend Opcache together with Redis is recommended or encouraged for GLPI.
Additionally, I’m still experiencing some slowness (about 10 seconds) when handling tickets and changes with many modifications, while simpler tickets load in about 1 second. Does anyone have any suggestions to improve the response time in these cases?
Are there any other configurations I should adjust or any potential misconfigurations I might have missed to further improve GLPI's performance?
Last edited by narque (Yesterday 17:31:37)
Offline
Pages: 1