404
edits
Ring Buffer Configuration Guide: Difference between revisions
→Performance
| Line 127: | Line 127: | ||
== Performance == | == Performance == | ||
=== Disk write and read Performance === | |||
Please note that one disk can have '''one''' shared ring buffer or be part of '''one''' cluster ring buffer. Hard disk drives have a very high constant write rate when only one write is active. | |||
The Allegro Network Multimeter has a ''write first'' policy on the ring buffer devices. When extracting a Pcap file from the ring buffer wh | |||
=== Concurrent '''Ring Buffer''' and live '''Pcap''' recording === | |||
Please note that HDDs are not made for 2 simultaneous write streams. The write rate will be very low if you capture a live Pcap to the single shared storage device while having an active ring buffer. Please use the browser download feature, different disks with the cluster ring buffer or pause the ring buffer while capturing the live Pcap. | |||
=== Buffering traffic peaks or disk slowdowns === | |||
Please note that most HDDs and SSDs do not have a guaranteed write rate. Especially HDDs via the USB or SATA3 protocol can have down-times of hundreds of milliseconds between writes. The buffer these downtimes, each ring buffer has a certain amount of memory to buffer traffic peaks. This buffer can be configured at the '''Settings''' of the '''Ring Buffer''' | |||
[[File:Ring buffer queue resize config.png|border|800px]] | |||
You can check if the queue length is big enough with the '''Bytes in Flight''' graph and the '''Dropped Bytes''' graph in the ring buffer statistics. | |||
[[File:Ring buffer data in flight.png|border|800px]] | |||
== Limitations == | == Limitations == | ||