Settings: Difference between revisions

Settings (view source)

Revision as of 07:29, 6 April 2020

3,592 bytes added , 6 April 2020

no edit summary

Soumar

1,775

edits

@@ Line 185: / Line 185: @@
 '''Tunnel view mode'''
+The Allegro Network Multimeter can decapsulate ERSPAN type II and type III traffic. In this mode all non-ERSPAN traffic is being discarded. On the dashboard a dropped counter will display dropped non ERSPAN packets for indication if this mode is active. The Multimeter will show the encapsulated content in all analysis modules.
+When capturing, packets with complete outer layer 2, layer 3, GRE and ERSPAN headers will be stored as seen on the wire.
 '''Database mode settings'''
+The database mode is a special analysis mode for high-performance Network Multimeters with multiple processors to increase the performance on such systems. It is normally enabled automatically but depending on the actual network traffic and system usage, some parameter tweak might be necessary to improve overall system performance.
+You should only change these parameters in discussion with the Allegro Packets support.
+These settings are only visible if your Network Multimeter is capable of running this mode.
 '''Network performance'''
+There are several network performance settings available to improve performance on high-performance systems in case of packet drops during very high receive bandwidth. They are only visible if your Network Multimeter is capable of changing these settings.
+* Max RX queues per socket: This setting specifies the amount of threads dedicated to read and write interactions with the network interface controllers. By increasing this value, network receive bandwidth can be increased before packet drops occur. By decreasing this value, data analysis will improve.
+The default setting of 2 RX queues is suitable for most configurations as data analysis typically needs much more processing ressources.
+* Use Hyper-Threading for RX queues: This setting allows enabling or disabling Hyper-Threading for the threads dedicated to read and write interactions with the network interface controllers.
+By disabling it, network performance can be improved as the RX queues will be distributed to physical CPU cores only.
+By enabling it, RX queues will also be distributed to virtual Hyper-Threading CPU cores which is not as efficient as physical CPU cores. By using Hyper-Threading, data analysis will improve as there are more CPU cores available for these tasks. Hyper-Threading is used by default.
+This is suitable for most configurations as data analysis typically needs much more processing ressources.
+* Preferred Network interface controller: This setting allows fine tuning of network and data analysis performance for dedicated network controllers. The selected set of network controllers will be preferred over the others.
+Usually the fastest or the network controller with the most traffic should be preferred. The ‘Auto’
+setting is used by default, preferring the fastest network controller.
+You should only change these parameters in discussion with the Allegro Packets support.
 '''Processing performance'''
+The processing performance may be modified on high-performance systems. This is only visible if your Network Multimeter is capable of changing this setting.
+* Processing performance mode: This setting allows for fine tuning processing performance. By using ‘Analysing’, as much processing ressources on all CPUs as possible are used for data analysis.
+By using ‘Capturing’, the focus will be on high data throughput and low latency for capturing purposes by using only the CPU where the preferred newtork controller is attached to.
+This has an impact on data analysis performance. ‘Analysing’ is used by default.
+You should only change this parameter in discussion with the Allegro Packets support.
 '''Packet ring buffer timeouts'''