Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DDAA711020 for ; Wed, 2 Apr 2014 01:31:03 +0000 (UTC) Received: (qmail 36269 invoked by uid 500); 2 Apr 2014 01:30:59 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 36115 invoked by uid 500); 2 Apr 2014 01:30:59 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 36106 invoked by uid 99); 2 Apr 2014 01:30:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2014 01:30:59 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Frederik.Nosi@postecom.it designates 62.241.5.183 as permitted sender) Received: from [62.241.5.183] (HELO smtp02.postecom.it) (62.241.5.183) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2014 01:30:54 +0000 Received: from VM-EXFE01.Postecom.local (192.168.98.84) by vm-exsmtp02.postecom.local (192.168.78.92) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Apr 2014 03:29:48 +0200 Received: from [192.168.1.139] (192.168.82.1) by VM-EXFE01.Postecom.local (192.168.98.34) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Apr 2014 03:30:32 +0200 Message-ID: <533B6838.6030107@postecom.it> Date: Wed, 2 Apr 2014 03:30:32 +0200 From: Frederik Nosi Organization: Postecom s.r.l. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: RES: Configuring limits of requests/sessions/threads in Tomcat References: <05317CC61C10DB449EBFF38B6AEFF6F540AC72E2E7@MGCLUSTMBXP6.scl.corp> <533B3045.4070903@christopherschultz.net> <05317CC61C10DB449EBFF38B6AEFF6F540AC7CD7C5@MGCLUSTMBXP6.scl.corp> In-Reply-To: <05317CC61C10DB449EBFF38B6AEFF6F540AC7CD7C5@MGCLUSTMBXP6.scl.corp> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [192.168.82.1] X-Virus-Checked: Checked by ClamAV on apache.org Hi Danilo, On 04/02/2014 02:37 AM, Danilo Amaral de Oliveira wrote: > Hello Chritopher, > > You make score. Exactly, I am waiting 500 users on the peak time. The archive is in a separated storage in our environment. So, I think that it is not a limiting factor. I will try some maxthreads configurations and stress situations to see if the server will could handle 500 users. If necessary I can increase the server memory and processing, we have robust cluster. Actually the server has 4 cores and 8gb of memory. First, this video is a static file right? If so, just put an nginx or such in front of you'r Tomcat, you dont need an application server for that, it's just like using a tank to shoot a mosquito :P > > At the same time, I am analyzing with security team if we could liberate a specific video in youtube in order to instead use JWPlayer the site use an embedded youtube video, so I take off the responsibility of tomcat to deliver the video and I can sleep in peace. hahha Well, this clever, bandwidth for free. > > Thank you all! > > > > Grupo Energisa > Danilo A. Oliveira > Analista Suporte Aplicacao TI - DPTO CORP. DE INFRAESTR. TI > e-mail: danilo.oliveira@energisa.com.br | tel: (32) 3429-6342 | cel: (32) 8452-9478 > > Esta mensagem contém informação confidencial. Se você a recebeu por engano, não divulgue ou copie seu conteúdo. Por favor, avise ao remetente imediatamente e apague-a do computador. > Privileged and confidential. If this message has been received by mistake, do not disclose or copy its contents. Please notify sender and delete immediately. > > > -----Mensagem original----- > De: Christopher Schultz [mailto:chris@christopherschultz.net] > Enviada em: terça-feira, 1 de abril de 2014 18:32 > Para: Tomcat Users List > Assunto: Re: Configuring limits of requests/sessions/threads in Tomcat > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Danilo, > > On 4/1/14, 2:03 PM, Danilo Amaral de Oliveira wrote: >> Next week we will deploy a institutional video to all company (more >> than 5k users) in a webpage in an application manges by the Tomcat >> 7.0.40. I have made a stress test through JMeter, simulating a lot of >> simultaneous access, and when the simultaneous access reaches >> 100 users the application stop answering. > What is your expected peak load? If you only need to handle 500 simultaneous users, then you should be fine. > >> I would like to know if I can set a max number (80, for example) of >> requests (maxsession or threads, I dunno) in order to configure the >> tomcat to send a warning page advising the user that the server is >> loaded and try again in few minutes if the limits reach the maximum >> value. > You can change the size of Tomcat's request processing pool. That's either "maxConnections" on your or, better yet, "maxThreads" in your . > > If you set maxThreads="80", then the 100th request will wait in a queue. You may get request timeouts at this point, which will be equivalent to the 100-user situation you describe above. > > What you really need is a CDN so your servers don't even handle the requests at all. Is there a place where you can upload your file that will be more scalable and/or faster? Something like Amazon S3 maybe? > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCAAGBQJTOzBFAAoJEBzwKT+lPKRYKjQP/0Ntz/ZT1ylSwMnFMCLFUDqC > 4C0eFUXJvPXu3Rr9+EjoSPRbX7r3FN5JMrx4SmwBwfxZhsjiyXksUMNVvUlW0QeD > CUtDsy4oYu3MM8BZqa2zqHtzDXQu8Qp8Hg3a5N0PQGWUqZCR/f2FOgR1fV+Zco2S > Av7ioK67dC/u2elUoC/2oUJ1J4xXSLlVOFRKGNB1i/EmkpDLi07tyLs/L2Y9TmWQ > VfUv5RETqdIA682OshfHJ5ViR5NbZKZVFwTA3H8+oPn5NtPBJ3UgT5hv4GmVYpgz > m4S6O/8CRJz33q+tz9N35e8Fx5JnU8l4Nwn6AfOW0tgUX9JO6V0+x6W7bvCjSrlH > vbmJYJjPynoP8Y1smAxGrNg8jwjQklTP5qTIRr2FBm2DZ0chJQYMAmbETShrYZu8 > n4na84JJ67gEMD2LV+ym5k7ma6gVmfCw3inT12kXtiwzC+d8vyxzdvToCT589cCJ > lRG5jhihpxPJTZtJ27db4ZxxgvG87ArQNhpvzEQCKnGa22/UkOaC56NZwzxbtfqb > 64u7Ok+Jn6z8fJBMeq9lxILUVJTsbgfD3wx4WqNH+f1D2U+LsSPXrm8xmP5DS5hd > KQ4GZUNT4kEApRCCSfqlzbi+BC2dwo7mm7zmhaMIV5Otu43Wda4fUpK2z+ZAwE35 > YJJvZvdzD8LkeMFiQz4G > =/hsP > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org