Well that's a toughy (and a friend and I have just faced the same thing
where we work).,
Danny Coward from Sun (i think) posted an up to date list of sites using
JSP technology.
If you look in the archives you can find the whole list, some highlights
from it were:
rewards.lycos.com
www.listen.com
www.starwars.com - yes really, the starwars site :)
www.enhydra.org
www.micron.net (reg.micron.net, smart.micron.net)
www.circuitcity.com BV
So some fairly major sites using the technology. Starwars.com using it
is particularly impressive.
and see comments below:
> "Todd L. Poole" wrote:
>
> My boss seems to have the "software engineer" background and is
> continuously critical about web technology that I work with. I develop
> web application using ASP and a database alone. I am not using any of
> my own components.
>
> Since I am learning java, I am finding it easier to understand and
> more logical than Microsoft's programming languages.
Absolutely true. - and easier to produce good designs as well.
> I would like to
> expand into using JSP, Servlets, and Beans, but my boss still thinks
> Java is slow and not as efficient as CGI programs written in C.
bwuahahaha CGI and C, ha ha.
> I
> think he is full of it and I would like to go back to him with proven
> results from other people using this technology in a situation where
> load balancing is an issue.
Ok. He thinks he understands code. Right lets see the big gains shall
we?
CGI and C
- process hit each time it runs
- database connection hit for each CGI
Java/Servlets
- NO process hit (so no context switch), no reloading of libraries, no
thrashing of memory on the machine, in fact the servlet engine may well
be reusing threads, so you don't even have the overhead of thread
creation. This can be a _big_ plus for reducing machine load
- use connection pooling - getting a db connection is _painfully_ slow.
If you want figures, try using a simple query like "select sysdate from
dual" against a db (in my case Oracle). On a five second test, repeating
the query each time: - get a connection for each query, result 10
invocations. - prepeare a statement and use a connection pool, result
900 invocations. - Yup, TWO orders of magnitude increase by using
connection pooling.
Other obvious statements are the fact that if you're using a database,
your speed will be entirely constrained by your database - after all,
when it hits the disk you're then working 1000 times slower than in
memory. i.e. the speed increases of compiled C are irrelevant next to
the slowness of a hard disk.
I can't say who it is, but I'm working on a project now where we're
building to scale to millions of users over time. That's not something I
would like to even consider doing in CGI and raw C.
>
> Until I am writing machine code - I will never please this guy, but I
> would like to prove him wrong just once with this.
>
> If you have any input, please share!
>
> Bored editing HTML pages....
So find a new boss ;)
Jari
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
