Monitoring performance of WFilter.

WFilter Monitoring Performance

WFilter is designed to monitor a network with no more than 1000 computers, and the available internet bandwidth of the entire network shall be no more than 100Mbit/s.

Since WFilter is software, the performance depends a lot on the hardware performance. Higher bandwidth requires faster CPU, and more monitored computers require more RAM. Therefore, we recommend you to provide 1M available RAM for each monitored computer.

Below is a performance test result for HTTP request of WFilter 3.3 file-based version:

# Computers Bandwidth Total HTTP Requests Recorded Percent CPU Memory
1 50 37.2M 16000 100% 35% 260,298K
2 100 35M 20000 100% 38% 280,576K
3 200 31M 40000 100% 58% 294,561K
4 400 33M 80000 100% 68% 372,786K
5 600 32.3M 120000 100% 80% 540,151K
6 1000 32.6M 200000 60% 99% 540,664K

As we can see from the above table, when monitored computers number reachs 1000, the “recorded percent” decreased to 60% suddenly. And we noticed the memory only slightly increased, so it shall because lack of memory. Therefore we added the monitoring computer RAM to 2G, and do the test again:

# Computers Bandwidth Total HTTP Requests Recorded Percent CPU Memory
7 1000 32.7M 200000 100% 90% 820,640K

And the test of WFilter 3.3 database version(SQL Server) performance has the similar result:

# Computers Bandwidth Total HTTP Requests Recorded Percent CPU Memory
1 50 34.9M 10000 100% 45% 197,392K
2 100 34.9M 20000 100% 45% 210,196K
3 200 31M 40000 100% 45% 270,960K
4 400 32.9M 80000 100% 45% 364,234K
5 1000 28.6M 200000 58.84% 100% 540,664K

The performance of 1000-user can also be improved by adding RAM of the monitoring computer.

Test Environment

1 Network 100M ethernet
2 Test Client Intel(R) pentium(R) Dual 1.80+1.80GHz , 1G RAM
3 Test Monitoring Server Intel(R) Celeron(R) 2.66GHz, 1G RAM
4 WFilter Version WFilter 3.3
5 Switch Tplink TL-SF1008

Facebook Comments

Leave a Reply