Performance Optimization Guide: Difference between revisions

Replaced 'Analyzer queue overcommit' with 'Ingress packet memory'
(Replaced 'Analyzer queue overcommit' with 'Ingress packet memory')
Line 68: Line 68:
This can be identified if packets are not processed while the system load is still not very high at the same time.  
This can be identified if packets are not processed while the system load is still not very high at the same time.  


If this occurs, the option '''Analyzer queue overcommit''' at '''Settings''' → '''Global settings''' → '''Expert settings''' can be enabled. It increases the queue size to be able to buffer network bursts during a short time period. The disadvantage is that the queues are overcommitted so it can happen that the network card does not have enough buffers available for incoming packets so some packets may not be forwarded in bridge. Therefore, this option is only recommended in '''Sink mode'''.
The '''Ingress packet memory''' provides a buffer for received packets which helps to avoid skipping packets in that situation. The historic usage of this memory can be viewed on the '''Info → System Info''' page.


[[File:Queue overcommit.png|1000px]]
If for some reason the amount of '''Ingress packet memory''' does not suffice it can be increased under '''Settings''' → '''Global settings''' → '''Expert settings.'''


=== Skipped packets due to analyzer load imbalance ===
=== Skipped packets due to analyzer load imbalance ===
122

edits