I've been using ntlmaps 0.9.8.8 as a parent proxy for
Proxomitron for a while and it worked fine. But after
an upgrade from ISA Server 2000 to 2004 SP1 in the org
I've noticed that CPU usage on my WS has become too
high during browsing. Even after moving from ntlmaps
0.9.8.8 to stable version 0.9.9.0.1 the situation
hasn't changed. It seems like ntlmaps polls parent
proxy (ISA 2004) too intensivly - it writes
*thousands* of debug strings "No server's data to send
to the client" to the log and pythonw.exe (v2.4.2
final) consumes 50% to 90% of a hyperthreaded CPU
time. The tests were done with Opera 9.00 and MSIE 6.0
(I now they both support NTLM but Proxomitron
doesn't). What's strange PARENT_PROXY_TIMEOUT setting
change from 15 to 3 doesn't seem to have an expected
effect on this...
And thanks for the great tool!
Denis <llama@bk.ru>
ntlmasp 0.9.9.0.1 debug logs