Configuring HTTP Proxy is sooo sloooooow!

[Guest]

[S3@N]

I have Endian 2.4.1 running on a VMware cluster with stacks of CPU & RAM and a nice fast storage system.  When configuring the HTTP proxy it takes several minutes to load the interface or to read the squid configuration.  During this time the CPU usage reported by top is typically around 3% - VMware sees occasional peaks (on the guest) higher than this but nothing over 30%. 

There are only 5 simple rules.

What gives? 

Have I missed something in the configuration?  Is there something I can do to improve performance?

[madhatt]

I can't answer your question except to say that this kind of thing happens to me often too.

[lo]

Can you post the output of

tail -f /var/log/messages /var/log/emi

when the HTTP proxy is restarting? It is really strange that it takes so long to start...

Bye

Lo