Re: [squid-users] Squid is very slow after moving to production environment

2018-04-14 Thread Amos Jeffries
On 13/04/18 05:55, Roberto Carna wrote: > People, I can't test de new proxy in the production environment > because I affect the users. I think is a good idea to add 10/15 users > to my new proxy, and test it with users from my IT area. Maybe the > problem is DansguardianI don't know. > > I'm

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-13 Thread MK2018
Roberto Carna wrote > Thanks to everybody... > > I've reviewed what you tell me. I've executed "squid -k parse" and > everything is ok, and I've restarted de Squid entire server. > > When I use the server with IP#1, it works OK, is fastbut when I > change its IP to IP#2 (the IP from the

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-10 Thread Amos Jeffries
On 11/04/18 07:10, Roberto Carna wrote: > Thanks to everybody... > > I've reviewed what you tell me. I've executed "squid -k parse" and > everything is ok, and I've restarted de Squid entire server. > > When I use the server with IP#1, it works OK, is fastbut when I > change its IP to IP#2

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-10 Thread Roberto Carna
Thanks to everybody... I've reviewed what you tell me. I've executed "squid -k parse" and everything is ok, and I've restarted de Squid entire server. When I use the server with IP#1, it works OK, is fastbut when I change its IP to IP#2 (the IP from the current Squid that I want to replace),

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-10 Thread joseph
hi also lower maximum_object_size_in_memory 4096 KB to maximum_object_size_in_memory 1 MB higher not wise - ** * Crash to the future ** -- Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-10 Thread Eliezer Croitoru
ect: Re: [squid-users] Squid is very slow after moving to production environment On 10/04/18 07:58, Roberto Carna wrote: > Dear Antony, both proxies are virtual machines in the same DMZthey > use the same DNS, the same firewall, the same Internet link, the same > IP but different MAC

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-10 Thread Matus UHLAR - fantomas
On 09.04.18 16:53, Roberto Carna wrote: Dear Periko, so here is what you ask to me: CPU x 8 RAM x 12 GB HD x 50 GB And this is /etc/squid/squid.conf file: cache_mem 4096 MB what is squid's real memory usage? It can be much much more than 4G, 4G is only cache, but squid also uses buffers

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-10 Thread Matus UHLAR - fantomas
On 10/04/18 07:58, Roberto Carna wrote: Dear Antony, both proxies are virtual machines in the same DMZthey use the same DNS, the same firewall, the same Internet link, the same IP but different MAC Address. On 10.04.18 22:09, Amos Jeffries wrote: FYI: there were issues some years back

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-10 Thread Amos Jeffries
On 10/04/18 07:58, Roberto Carna wrote: > Dear Antony, both proxies are virtual machines in the same DMZthey > use the same DNS, the same firewall, the same Internet link, the same > IP but different MAC Address. FYI: there were issues some years back with VMs that were cloned operating VERY

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-09 Thread Rafael Akchurin
e.it> Cc: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Squid is very slow after moving to production environment Dear Antony, both proxies are virtual machines in the same DMZthey use the same DNS, the same firewall, the same Internet link, the same IP but different MAC Addre

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-09 Thread Periko Support
Try to add this setting: dns_v4_first on Latter check settings and see if there is no issue with the setting. squid -k parse. Then reload: squid -k reconfigure Test. On Mon, Apr 9, 2018 at 1:05 PM, Antony Stone wrote: > On Monday 09 April 2018 at

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-09 Thread Antony Stone
On Monday 09 April 2018 at 21:53:26, Roberto Carna wrote: > I've just changed the new proxy to test environment and it works very > well againI get lost. What does that change involve? I'm trying to understand what is different between your "test" environment and your "production"

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-09 Thread Antony Stone
On Monday 09 April 2018 at 21:58:52, Roberto Carna wrote: > Dear Antony, both proxies are virtual machines in the same DMZthey > use the same DNS, the same firewall, the same Internet link, the same > IP but different MAC Address. So, what is different between "test" and "production"?

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-09 Thread Roberto Carna
Dear Antony, both proxies are virtual machines in the same DMZthey use the same DNS, the same firewall, the same Internet link, the same IP but different MAC Address. Firewall rules are the same too. The new proxy is slow because when users try to go to a web page, it is very slow in

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-09 Thread Antony Stone
On Monday 09 April 2018 at 21:00:21, Roberto Carna wrote: > Dear, I have implemented a server with Dansguardian 10.2.1.1 and Squid > 3.5.23-5. > > I've tested it with 5 users for along 2 months and always it worked OK. > > But today when a moved it to production environment, it worked but >

[squid-users] Squid is very slow after moving to production environment

2018-04-09 Thread Roberto Carna
Dear, I have implemented a server with Dansguardian 10.2.1.1 and Squid 3.5.23-5. I've tested it with 5 users for along 2 months and always it worked OK. But today when a moved it to production environment, it worked but very very slow. I've just changed hostname and IP, in order to match with