Hi,
If you want to use Tomcat for high loads, I suggest you to use apache/mod_jk
and a cluster of Tomcat instances.
With this solution you'll have load-balancing and failover for a lot of users.
I don't use a HP very powerful, so, for the performances, I don't know if it is
better to have one
1a) It depends on your code. TOmcat can handle it but only if your code can
also scale.
1b) Free: Jmeter, seige, apache ab - it depends on the type of test
2) See the faq or wiki
http://jakarta.apache.org/tomcat/faq/performance.html
http://wiki.apache.org/jakarta-tomcat/UsefulLinks
3) Maybe.
before you can answer that question, you need to know what the average
and peak concurrent requests is. without that 300-400 concurrent users
doesn't mean much.
If those 400 users hit the site once per minute average over 30
minutes, it would mean 12,000 requests in 30 minutes. Even if the
user
that the way the application works and its design is scalable and efficient
are well taken.
Thanks again,
Haytham Samad
-Original Message-
From: Chakravarthy, Sundar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 10:48 AM
To: Tomcat Users List
Subject: RE: Tomcat Scalability
On Mon, Mar 03, 2003 at 11:32:07PM -0600, Haytham Samad wrote:
I have searched in the mail archive and did not find a comprehansive
answer to the settings one needs to look for to make sure Tomcat
scales with an increasing number of users.
You'll probably get more milage out of
Haytham Samad wrote:
Anything on can do to set Tomcat up to scale?
I am running Tomcat as a service on Win 2K.
You could start by running it on Linux instead to save all that memory
and processor power that Windows consumes :)
But seriously, I'm interested in hearing how Tomcat can scale, too.
it's going to be hard to summarize tuning in a
paragraph or even a few pages. If there aren't any
existing weblogs to tell you the amount of traffic it
will get, you're only good solution is to implement
logging and monitoring.
then everyday look at how the site is performing,
graph the results
There are a lot of companies using Tomcat in
production and some of them are large sites that get 1
million+ page views a day. Just because there are a
lot of calls, it doesn't necessarily mean it's a
problem.
scaling a website to handle millions of hits a day
takes time and thorough testing. If
Scability/Perfomance/Memory was talked about many times in the past. I
am still digging up good threads/sites with respect to the FAQ, but here
is what I have so far, each page has links to the appropriate discussion
thread in the tomcat-user lists.
Performace:
Users List
Subject: Re: Tomcat Scalability
Scability/Perfomance/Memory was talked about many times in the past. I
am still digging up good threads/sites with respect to the FAQ, but
here
is what I have so far, each page has links to the appropriate
discussion
thread in the tomcat-user lists
one more note. Persistence is the only effective tool
for high performance! No amount of money or talent can
beat persistence when it comes to making sure your
website works reliably and responds within a set time.
peter
--- Tim Funk [EMAIL PROTECTED] wrote:
Scability/Perfomance/Memory was
to boost Tomcat, unless I absolutely have
to.
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 9:28 AM
To: Tomcat Users List
Subject: Re: Tomcat Scalability
one more note. Persistence is the only effective tool
for high performance
I have the following in production:
Tomcat 4.1, JDK 1.3.1, and MySQL on a Dual CPU Sun 250 app server and Apache
using mod_jk 1.2 on a separate server. We are now getting 4 weeks continuous uptime.
I stop and restart Tomcat once each month because the minimum memory the java heap
uses over time
I would say Tomcat 4.1.x probably would be good for you mainly if you
uses lots of Taglibs, if they actually will work on it.
Btw, I'm still using 4.0.x... how everybody is doing with 4.1.x? I
heard is too much buggy for production right now.
On Fri, 2002-10-25 at 12:20, Glenn Nielsen wrote:
Hi,
I would say Tomcat 4.1.x probably would be good for you mainly if you
uses lots of Taglibs, if they actually will work on it.
Btw, I'm still using 4.0.x... how everybody is doing with 4.1.x? I
heard is too much buggy for production right now.
We're using 4.1.10-LE and 4.1.12-LE in
[EMAIL PROTECTED]
Assunto: Re: Tomcat Scalability - Long
I would say Tomcat 4.1.x probably would be good for you mainly if you
uses lots of Taglibs, if they actually will work on it.
Btw, I'm still using 4.0.x... how everybody is doing with 4.1.x? I
heard is too much buggy for production right
Hi,
Does anyone have any solid information about the scalability of Tomcat?
It
seems very limiting to me, but that is hopefully due to improper
What are you looking for by solid information? ;)
Here are some details about one of our environments:
An 18-CPU Sun Ultra Enterprise-class server,
We have a similar hardware setup (PIII 1GHz 512M) but running Tomcat 4.0.4
on Win2k/IIS and accessing a DB2 database on a separate iSeries server.
The system is used by our sales reps in the US and Canada (about 30) over a
VPN, so it can see activity at any time. It never really gets hammered
Brandon Cruz wrote:
Does anyone have any solid information about the scalability of
Tomcat? It
seems very limiting to me, but that is hopefully due to improper
configuration. Here is our situation and what seems to be happening
under a
small amount of stress.
Try upgrading to either:
-
We host 15 separate Tomcat instances (3.1) on a single machine. The apps
use MySQL.
The machine is dual-P3 1GHz, 2GB RAM. Red Hat 7.2, Apache 1.3.26. The
connector is mod_jserv. Not sure which JDK, probably 1.3.
The usage is high, all of the apps are graphics manipulation apps serving
users
If your kernel is not in the 2.4.18-2.4.19 range, you should update the
kernel. 7.1 is pretty old. It shipped with a very early 2.4 series kernel.
-Original Message-
From: Brandon Cruz [mailto:bcruz;norvax.com]
Sent: 24 October, 2002 1:36 PM
To: Tomcat Users List
Subject: Tomcat
Hi.
I am still on kernel 2.4.2 and it seems okay.
May I ask why we need to upgrade to 2.4.19 ?
Sexton, George wrote:
If your kernel is not in the 2.4.18-2.4.19 range, you should update the
kernel. 7.1 is pretty old. It shipped with a very early 2.4 series kernel.
-Original
Of
[EMAIL PROTECTED]
Sent: 24 October, 2002 2:06 AM
To: Tomcat Users List
Subject: Re: Tomcat Scalability - Long
Hi.
I am still on kernel 2.4.2 and it seems okay.
May I ask why we need to upgrade to 2.4.19 ?
Sexton, George wrote:
If your kernel is not in the 2.4.18-2.4.19 range, you should
Hi,
Just a suggestion.
Why not use Apache to take care of all the security? Ie have home
directories for each user and only the user has access to his/her home
directory, then apache can use a standard like http://localhost/~user and
everything is sepearate. It would be a lot easier to
The permission denied can be generated one of two ways.
First, the catalina.policy file must grant the correct FilePermission.
Even if the correct FilePermission is granted in catalina.policy, you
still have to comply with normal unix file ownership/permissions.
If it is a catalina.policy
I should clarify. Security in this case means a student should not
be able to view the source code of another student. Because we are
exporting the files but they still need to be accessible by Tomcat, each
user directory is 570 tomcat:user and all files inside are world
readable. This allows
and
thus has access to everything.
Well hope you get a solution.
Nicholas Orr
-Original Message-
From: Pat Schaider [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 10 September 2002 4:57 PM
To: Tomcat Users List
Subject: RE: Tomcat scalability question
I should clarify. Security
27 matches
Mail list logo
