Notification Server Queues - Is One More Important Than the Other?
Filed under:
Notification Server
Productivity
Submitted by BRING on 21 August, 2008 - 09:25.
EvtQueue, EvtQFast, EvtQLarge, and EvtQSlow. These folders within the Altiris folder structure are the lifeblood of data processing for your Notification Server.
One might wonder if EvtQueue is more important than EvtQFast, EvtQLarge, or EvtQSlow? Or could EvtQFast get preferential treatment? What happens when multiple NSE files are captured at the same time - does one queue get a priority over any other and if so, what is that priority?
Well, in the interest of fair play, the Notification Server does not play favorites. No queue has priority over another. Each one has been assigned one or more processor threads, (with the exception of EvtQLarge), and the remaining queues all process concurrently. The default threads for each queue are different however. EvtQFast has 10, EvtQueue has 3, and EvtQSlow has 1.
So maybe EvtQFast is the preferred child? Hmmm......
(26 votes)
- Login or register to post comments
- 2150 reads
- Printer-friendly version
Queues are mainly broken down for size
The big difference between these queues is the size of the files stored in them.
Right from the Notification System Foundation Class manual:
EvtQFast: Processes NSE files smaller than 15KB
EvtQSlow: Processes large NSE files between 1MB to 20MB by default)
EventQueue: Processes NSe files in between thresholds of EvtQFast and EvtQSlow (between 15KB and 1MB by default)
EvtQLarge: Processes files larger than 20MB by default.
And to ease processing
Because of the different sizes and the different amount of threads assigned to each queue this eases processing.
You can adjust how many threads are watching each queue by either editing the coresettings.config file or by using the NSConfigurator, my perfered method.
Jonathan Jesse
Director of Training
ITS Partners