-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Victor Sudakov wrote:
And about the basic issues that you were having with performance,
does it help to run Kerberos instead of NTLM (it should...)?
I have even moved squid to a new virtual machine (FreeBSD
9.3-RELEASE under
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
What is the network load? how many users?
Have you been using workers at all in the past?
Can you see the avg requests per second on the cache manager page?
Eliezer
On 10/22/2014 09:02 AM, Eugene M. Zheganin wrote:
Hi.
I was using the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/23/2014 02:40 AM, Amos Jeffries wrote:
If you are seeing this old content constantly or round-robin style
between page loads you can use west.squid-cache.org temporarily in
the URLs instead of www.
Amos
It's the same issue for me:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/10/2014 7:27 p.m., Victor Sudakov wrote:
Victor Sudakov wrote:
And about the basic issues that you were having with
performance, does it help to run Kerberos instead of NTLM
(it should...)?
I have even moved squid to a new virtual
Same here, i'm waiting the right time to go to the customer and try the debug
suggested by Amos Jeffries on 3.4.x codes to help to find where is the
performance issue.
--
View this message in context:
On Thu, Oct 23, 2014 at 3:10 PM, Yassin CHOUCHANE frechdes...@gmail.com wrote:
root [~] nslookup cafeServer
Server: 192.168.1.3
Address:192.168.1.3#53
Name: cafeServer.sonsofanarchy.fr
Address: 192.168.1.50
but when i lunch it on my webrowser i have the message
Server
