[ZBX-25640] Problem tag filter benefits of extra indexes Created: 2024 Nov 29 Updated: 2025 Mar 19 |
|
Status: | READY TO DEVELOP |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 6.0.36, 7.0.6 |
Fix Version/s: | 7.0.12rc1, 7.2.6rc1, 7.4.0beta1 (master) |
Type: | Problem report | Priority: | Minor |
Reporter: | Aigars Kadikis | Assignee: | Vladimirs Maksimovs |
Resolution: | Unresolved | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() |
||||||||
Issue Links: |
|
||||||||
Team: | |||||||||
Sprint: | Sprint candidates |
Description |
In version 7.0, if User Groups use “Problem tag Filter” like this: Users experience a very high load time, around 30 seconds, this makes the Problems page unusable. create index items_11 on items (itemid,hostid,key_(100)); create index functions_4 on functions (triggerid,itemid); After the creation of these two indexes, the load time passed from 30 seconds to 0.5 seconds. Similar benefit happens on Zabbix 6.0, where the outcome is 1.9 (without) VS 0.3 (with) seconds. In Addition to that I see that with version 7 , a lot of TMP table are created on disk by MariaDB , so we need to increase the tmp-table-size parameter to 4GB . Size stats about tables sizes: zabbix7db-size.txt |