-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Leon,
On 7/10/14, 3:27 PM, Leon Rosenberg wrote:
> answering only to the one directed at me (or so I think):
;)
> On Thu, Jul 10, 2014 at 4:09 PM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 7/10/14, 5:40 PM, André Warnier wrote:
> Christopher Schultz wrote: ...
>
>>
>> Interesting... load average is a crude measure of activity; I
>> suppose that having those timeouts means that there is activity
>> on a thread even when the
Christopher Schultz wrote:
...
Interesting... load average is a crude measure of activity; I suppose
that having those timeouts means that there is activity on a thread
even when there is no real "work" to be done. I do recommend leaving
the timeouts set to their defaults (-1 = infinite).
In
answering only to the one directed at me (or so I think):
On Thu, Jul 10, 2014 at 4:09 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Leon,
>
> > If you have very fast connections, go for a smaller amount. If you
> > have kee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hernán,
On 7/10/14, 11:19 AM, doomito wrote:
> Hi! I already did some testing. First of all, setting the
> connectiontimeout was not a good idea :) While the servers seems to
> be able to handle the same load, the load average went up.
Interesting.
http, we use APACHE since we have quite a lot of rules. We also
use mod_deflate, mod_expires and other apache modules.
--
View this message in context:
http://tomcat.10.x6.nabble.com/VERY-HIGH-TRAFFIC-TUNING-tp5019838p5019923.html
Sent from the Tomcat - User mailing list archive at Nabble.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hernán,
On 7/9/14, 11:50 AM, doomito wrote:
> Thank you for the answer. I will begging experimenting on 1 box
> with this configuration:
>
>
> emptySessionPath="true" redirectPort="8443" maxThreads="2048"
> minSpareThreads="32" connectionTimeout
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Leon,
On 7/9/14, 3:16 AM, Leon Rosenberg wrote:
> On Wed, Jul 9, 2014 at 4:47 AM, Hernán Marsili
> wrote:
>> For the past 4 years we has been working with a 'stable'
>> configuration in which we put APACHE in front of TOMCAT7
>> (previously Tomcat6
doomito wrote:
Thank you for the answer. I will begging experimenting on 1 box with this
configuration:
emptySessionPath="true" redirectPort="8443" maxThreads="2048"
minSpareThreads="32" connectionTimeout="2" keepAliveTimeout="1"
enableLookups="false" request.registerRequests="fal
od_jk.
--
View this message in context:
http://tomcat.10.x6.nabble.com/VERY-HIGH-TRAFFIC-TUNING-tp5019838p5019875.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-uns
Hi.
This kind of question is very difficult to answer reasonably, for anyone that is not you
and does not have direct access to your system, to see what happens, when it happens.
The general and reasonable answer would be that you need to use some monitoring tools, to
find out where exactly the
On Wed, Jul 9, 2014 at 4:47 AM, Hernán Marsili wrote:
> Hi,
>
Hello Hernán,
>
> For the past 4 years we has been working with a 'stable' configuration in
> which we put APACHE in front of TOMCAT7 (previously Tomcat6) with mod_jk
> connector. We usually serve high traffic sites with about 7000
Hi,
For the past 4 years we has been working with a 'stable' configuration in
which we put APACHE in front of TOMCAT7 (previously Tomcat6) with mod_jk
connector. We usually serve high traffic sites with about 7000 to 10.000
concurrent users per box (8gb RAM / 4 vcpu) (50.000 active users total).
13 matches
Mail list logo