|
When capturing data from a large and busy network segment, you
should keep in mind that processing thousands of packets per second
might considerably increase the CPU usage and make the application
less responsive. The best way to optimize the program's performance
is to use rules to filter out the packets you do not need to
monitor. For example, sending a 50 MB file between two machines on
your WLAN can generate approximately 40,000 NetBIOS packets with
the data transfer rate of 5 MB per second, which can be a heavy
load for the application. However, normally you do not to need to
view every NetBIOS packet being sent, so you can configure CommView
for WiFi to capture IP packets only. CommView for WiFi has a
flexible system of filters, and you can fine-tune the application
to display only the packets that you really need. In addition, if
you are interested in the statistics information only (those green
histograms, pie charts, and hosts tables), you can use the "Suspend
packet output" menu command, which allows you to have statistical
data without real-time packet display.
The factors that improve the program's performance:
·A
fast CPU (Intel Core i7 is recommended)
·RAM
size (8 GB and higher recommended)
·Using
rules to filter out unnecessary traffic
|
