[ZBXNEXT-8166] Thread based pre-processing workers Created: 2022 Dec 20 Updated: 2025 Jan 10 Resolved: 2023 Mar 09 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | None |
Fix Version/s: | 6.4.0rc1, 6.4 (plan) |
Type: | New Feature Request | Priority: | Trivial |
Reporter: | Andris Zeila | Assignee: | Andris Zeila |
Resolution: | Fixed | Votes: | 7 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() ![]() ![]() |
||||||||||||
Issue Links: |
|
||||||||||||
Team: | |||||||||||||
Sprint: | Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023), Sprint 98 (Mar 2023) | ||||||||||||
Story Points: | 8 |
Description |
Currently preprocessing workers are implemented as separate processes, which makes harder to exchange complex data. This led to batching dependent item preprocessing on workers when preprocessing cache was added, severely hurting preprocessing parallelism in some cases. To improve this situation preprocessing manager/workers must be rewritten to use thread based workers. The design goal is to replicate current preprocessing with minimum overhead and maximum parallelism. In future this could be improved further by moving user macro resolving to workers and having dynamic worker management (creating/destroying workers as required by the preprocessing load). |
Comments |
Comment by Andris Zeila [ 2023 Feb 17 ] |
Released
|
Comment by Martins Valkovskis [ 2023 Feb 24 ] |
Updated documentation: |