6 Mar
2011
6 Mar
'11
9:55 a.m.
On Fri 04 Mar 2011, Alan DeKok wrote:
Chris Hellberg wrote:
It's certainly easier this way. But the same problem exists - 99% CPU for server-side pools and 4% for no server-side ippool usage.
Well... how many packets are you sending to it? And have you tried just "key = %{Calling-Station-Id}" ?
If it's using 99% CPU for MD5, there's likely a reason. The system either has no CPU power, or it's receiving 1000's of packets/s.
Hello Chris I have also had problems in the past with ippool not scaling which is why the sql based ippool module exists ;-) Cheers -- Peter Nixon http://peternixon.net/