
gits.systems at gmail
Jul 28, 2012, 11:25 PM
Post #8 of 15
(625 views)
Permalink
|
Thanks Abraham, i really appropriated it brother. Seems when i add these configuration to the config it's get the server offline immediately! -p thread_pools=8 \ -p thread_pool_max=5000 \ -p thread_pool_min=100 \ -p thread_pool_add_delay=2 \ -p sess_timeout=60" Kind Regards, -J On Sun, Jul 29, 2012 at 9:20 AM, Abraham Cruz Sustaita < abraham.sustaita [at] buscacorp> wrote: > I'm attaching my configuration file. May be it can help you. > > > Abraham Cruz Sustaita > > Leader Development > > Mail: abraham.sustaita [at] buscacorp > Ph: +52 (664) 200.2213 > F: +52 (664) 200.2234 > M: +52 (664) 123.0312 > Calle Brasil No. 8471. Col. Juárez, Tijuana Baja California, CP 22040 > > BuscaCorp.com <http://www.buscacorp.com/> | LevelUp.com<http://www.levelup.com/> > | MetaTube.com <http://www.metatube.com/> | SanDiegoRed.com<http://www.sandiegored.com/> > | Tarreo.com <http://www.tarreo.com/> > > This e-mail message is intended only for the personal use of the > recipient(s) named above. This message may be an attorney-client > communication and as such privileged and confidential. If you are not an > intended recipient,you may not review, copy or distribute this message. If > you have received this communication in error, please notify us immediately > by e-mail and delete the original message. > > > Este mensaje es para uso personal de(los) destinatario(s) a cuyos nombres > se dirige. Este mensaje puede ser comunicación abogado-cliente y por tanto > es privilegiado y confidencial. Si usted no es la persona a quien se > intentó enviar este mensaje, no debe revisarlo, copiarlo o distribuirlo en > forma alguna. Si ha recibido este mensaje por error, por favor notifíquelo > inmediatamente por email y destruya el mensaje original. > > > > 2012/7/28 GITSS <gits.systems [at] gmail> > >> It's fine bro, hope i can help you if you need any help. >> >> Hence here when i start Varnish i cannot allocate memory or do anything >> until i stop it! >> >> >> ------------------------------------------------------------------------------------------------------------- >> root [at] sr [/home/userwww]# /etc/init.d/varnish restart >> Stopping varnish HTTP accelerator: [ OK ] >> Starting varnish HTTP accelerator: [ OK ] >> root [at] sr [/home/userwww]# service httpd restart >> root [at] sr [/home/userwww]# w >> 09:15:41 up 2 days, 22:05, 1 user, load average: 0.01, 0.04, 0.06 >> USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT >> j0 pts/0 46.248.192.217 07:56 4:02 1.34s 0.01s sshd: j0 >> [priv] >> root [at] sr [/home/userwww]# php -v >> Out of memory >> root [at] sr [/home/userwww]# /etc/init.d/varnish stop >> Stopping varnish HTTP accelerator: [ OK ] >> root [at] sr [/home/userwww]# service httpd restart >> root [at] sr [/home/userwww]# w >> 09:15:53 up 2 days, 22:05, 1 user, load average: 0.08, 0.05, 0.06 >> USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT >> j0 pts/0 46.248.192.217 07:56 4:14 1.34s 0.01s sshd: j0 >> [priv] >> root [at] sr [/home/userwww]# php -v >> PHP 5.3.14 (cli) (built: Jul 25 2012 19:12:57) >> Copyright (c) 1997-2012 The PHP Group >> Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies >> with eAccelerator v0.9.6.1, Copyright (c) 2004-2010 eAccelerator, by >> eAccelerator >> with the ionCube PHP Loader v4.0.12, Copyright (c) 2002-2011, by >> ionCube Ltd., and >> with Zend Guard Loader v3.3, Copyright (c) 1998-2010, by Zend >> Technologies >> root [at] sr [/home/userwww]# >> >> ------------------------------------------------------------------------------------------------------------- >> >> Is there anyone could assist me in this issue? >> >> Kind Regards, >> -J >> >> >> >> On Sun, Jul 29, 2012 at 9:14 AM, Abraham Cruz Sustaita < >> abraham.sustaita [at] buscacorp> wrote: >> >>> Im newbbie also. I have some questions on the mail list. Let me look for >>> them >>> >>> >>> El sábado, 28 de julio de 2012, GITSS escribió: >>> >>>> Thanks Abraham, long work day, is there any helpful rules for VCL can >>>> you share with us? am newbie with Varnish and looking to Speed my website >>>> for huge traffic, i have each day more than 30.000 and when the visitor >>>> comes to 2000 per second the web-server comes down, hence am looking for a >>>> good rules for VCL? >>>> >>>> Kind Regards, >>>> -J >>>> >>>> >>>> >>>> On Sun, Jul 29, 2012 at 9:01 AM, Abraham Cruz Sustaita < >>>> abraham.sustaita [at] buscacorp> wrote: >>>> >>>> You are missing one \ after -s file... >>>> >>>> El sábado, 28 de julio de 2012, GITSS escribió: >>>> >>>> Hello, >>>> >>>> I'm using varnish-2.0.6-2.el5-x86_64 on CentOS 5.8 64-bit, when i run a >>>> restart command i recieve this error >>>> >>>> root [at] orien [/etc/varnish]# service varnish restart >>>> /etc/sysconfig/varnish: line 42: -p: command not found >>>> Stopping varnish HTTP accelerator: [ OK ] >>>> Starting varnish HTTP accelerator: [ OK ] >>>> root [at] orien [/etc/varnish]# >>>> >>>> to check /etc/sysconfig/varnish file >>>> >>>> DAEMON_OPTS="-a :80 \ >>>> -T localhost:6082 \ >>>> -f /etc/varnish/orient.sameerbook.com.vcl \ >>>> -u varnish -g varnish \ >>>> -s file,/var/lib/varnish/varnish_storage.bin,1G" >>>> -p thread_pools=8 \ >>>> -p thread_pool_max=5000 \ >>>> -p thread_pool_min=100 \ >>>> -p thread_pool_add_delay=2 \ >>>> -p sess_timeout=60" >>>> >>>> >>>> The -p command i just add it from this thread: >>>> http://techshihab.wordpress.com/2012/03/05/install-varnish-cache/ >>>> >>>> As i beleave these command to make the Varnish accept more connection >>>> quickly for servers who had a huge connection ( ex: my website had each day >>>> more than 30.000 visitor per day and a 1500/2000 live visitor sometimes per >>>> second ). >>>> >>>> Hence i don't know if these commands are right or not as i see the >>>> error when i did restart for varnish. >>>> >>>> *Please let me know if there any other commands/feature for Varnish to >>>> handle huge connection like mine. >>>> >>>> Kind Regards, >>>> -J >>>> >>>> >>>> >>>> -- >>>> >>>> Abraham Cruz Sustaita >>>> >>>> Leader Development >>>> >>>> Mail: abraham.sustaita [at] buscacorp >>>> Ph: +52 (664) 200.2213 >>>> F: +52 (664) 200.2234 >>>> M: +52 (664) 123.0312 >>>> Calle Brasil No. 8471. Col. Juárez, Tijuana Baja California, CP 22040 >>>> >>>> BuscaCorp.com <http://www.buscacorp.com/> | LevelUp.com<http://www.levelup.com/> >>>> | MetaTube.com <http://www.metatube.com/> | SanDiegoRed.com<http://www.sandiegored.com/> >>>> | Tarreo.com <http://www.tarreo.com/> >>>> >>>> This e-mail message is intended only for the personal use of the >>>> recipient(s) named above. This message may be an attorney-client >>>> communication and as such privileged and confidential. If you are not an >>>> intended recipient,you may not review, copy or distribute this message. If >>>> you have >>>> >>>> >>> >>> -- >>> >>> Abraham Cruz Sustaita >>> >>> Leader Development >>> >>> Mail: abraham.sustaita [at] buscacorp >>> Ph: +52 (664) 200.2213 >>> F: +52 (664) 200.2234 >>> M: +52 (664) 123.0312 >>> Calle Brasil No. 8471. Col. Juárez, Tijuana Baja California, CP 22040 >>> >>> BuscaCorp.com <http://www.buscacorp.com/> | LevelUp.com<http://www.levelup.com/> >>> | MetaTube.com <http://www.metatube.com/> | SanDiegoRed.com<http://www.sandiegored.com/> >>> | Tarreo.com <http://www.tarreo.com/> >>> >>> This e-mail message is intended only for the personal use of the >>> recipient(s) named above. This message may be an attorney-client >>> communication and as such privileged and confidential. If you are not an >>> intended recipient,you may not review, copy or distribute this message. If >>> you have received this communication in error, please notify us immediately >>> by e-mail and delete the original message. >>> >>> >>> Este mensaje es para uso personal de(los) destinatario(s) a cuyos >>> nombres se dirige. Este mensaje puede ser comunicación abogado-cliente y >>> por tanto es privilegiado y confidencial. Si usted no es la persona a quien >>> se intentó enviar este mensaje, no debe revisarlo, copiarlo o distribuirlo >>> en forma alguna. Si ha recibido este mensaje por error, por favor >>> notifíquelo inmediatamente por email y destruya el mensaje original. >>> >>> >> >
|