You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@jakarta.apache.org by Peter Bryant <pb...@bigfoot.com> on 1999/11/13 06:07:39 UTC
Servlet Performance
Hi All.
I've been using Jserv in a development and beta environment for a while now,
in future I'd like to go with Tomcat.
We're soon moving into production mode where we expect to be serving
millions of pages daily.
I've posted an article at http://www.javalobby.org trying to get feedback on
the best hardware, OS, servlet engine deployment environment. If anyone on
the list would care to contribute to this topic, that would be great.
If anyone here has experience with deployment of high mega-hit servlets I'd
be interested in getting in touch directly.
Peter Bryant
Re: Servlet Performance
Posted by Paul Lamb <pa...@redfork.com>.
SoapBox todaysRant = new SoapBox("performance");
My best advice is to rely on your own tests and base your decisions on that.
Picking the initial hardware/os combination can be really tough; but the
software you use on top of that can have equally huge consequences on
performance.
Here's a few things to watch for:
1. Make sure you get a feel for the overhead, both cpu and latency, added by
the connector from the webserver to the servlet engine, as this can vary
greatly and cause a significant impact in overall performance. Since you can
download evals of just about every webserver, servlet engine or application
server out there, try as many as possible.
2. Memory leaks and thread sync issues can be both hard to find and deadly
in a high volume site. Once you get the production site up, run it under a
load-generator for at least several days to a week to hopefully find some of
these problems early.
3. I've seen order or magnitude changes in performance by just updating the
jdbc drivers. Are you using a connection pool? What about a global values
pool?
4. Be careful with single-threaded servlets. If you can't avoid them, then
make sure your servlet environment lets you set how many it creates in the
pool.
5. Make sure you give your servlet environment plenty of memory. If the site
is really busy and the garbage collector doesn't get to run very often then
you need lots and lots of available memory.
6. If you do have performance problems and you've creating your own testing
methodology you'll have a great start for reproducing and pin-pointing the
problem. I've had situations where it was tough to decide if it was an os,
webserver, jvm, servlet environment or my own code's problem.
7. Web site traffic is not constant. How well/poorly does you site handle
spikes and hit storms. I've got B2B sites that see 80% of their traffic in a
half hour in the morning and 45-minute window in the afternoon.
I've spent the last month evaluating both open source and commercial
solutions for a client and I can say that I'm glad I did real testing
instead of going with my usual biases. Also, as things are _today_ (the gap
is narrowing), the best performance I have found is in the commercial
products. If you just need basic servlet/jsp environment take a look into
either JRun from Allaire or ServletExec from New Atlanta and try them with
multiple web servers (Apache, Netscape, Zues, IIS) under different operating
systems.
If you are doing a commercial site that going to see huge volumes, make sure
you have a reasonably quick and painless way to move your software up to an
application server and larger hardware. I've heard from more than one app
server vendor that many of their sales are due to someone writing a site to
one of the basic servlet engines and then the site gets featured in USA
Today or the WSJ and performance melts down. I've seen developers loose jobs
and clients because they didn't have a backup plan; one of the side-effects
of people that clean up these situations is that they are usually interested
in making you look stupid so they can takeover.
Due to non-disclosure limitations, I can't post anything specific about our
test results or the resulting choices. But I can't stress enough: do your
own testing. Be wary of vendors benchmarks du jour; many either aren't
reproducable or require the use of software that is in either beta form or
isn't available at all. It's amazing how many of the spec web or jvm number
are based on beta software; I'd really love to see if the numbers would hold
up the same in actual release code--not that any vendor would create a beta
of a product that would perform incredible well on the benchmark.
Paul Lamb
> Hi All.
>
> I've been using Jserv in a development and beta environment for a while
now,
> in future I'd like to go with Tomcat.
>
> We're soon moving into production mode where we expect to be serving
> millions of pages daily.
>
> I've posted an article at http://www.javalobby.org trying to get feedback
on
> the best hardware, OS, servlet engine deployment environment. If anyone
on
> the list would care to contribute to this topic, that would be great.
>
> If anyone here has experience with deployment of high mega-hit servlets
I'd
> be interested in getting in touch directly.
>
> Peter Bryant
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
Solaris - Help.
Posted by Soni Dhiraj <ds...@uswest.com>.
Hi Guys,
My platform is Solaris + NES3.62. I ran into all
sorts of problems in making jakarta work .I built nsapi_redirector.so
from Makefile.solaris(under
jakarta-tomcat/src/native/iis_netscape).
I had to modify makefile so that it compiled. My version
of makefile is attached(had to remove prepare or sthg.).
It compiled successfuly after that. Now ,I did exactly as
the netscape-howto said. SEE the FAQ for that.
Now, I am STUCK here: I start jakarta by startup.sh
then point browser at http://machine:8007/examples
or even at http://machine:8007 , the window where i
start jakarta gives this ERROR:
I have no clue whats going on,but i think atleast jakarta is getting
invoked since i get this error:
HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
java.io.IOException: Stream broken
at
org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:339)
at
org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:127)
at
org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:334)
at java.lang.Thread.run(Thread.java)
I would really like to get jakarta work on Solaris ,
Please help.
Thanks,
Dhiraj Soni.