Hmm, I was hoping so. Do you have any numbers (not for comparisation,
just absolute ones)?
I agree one should reduce such overhead (and corresponding maintenance)
to a minimum.
On 07/06/2010 03:30 PM, Dustin Whitney wrote:
>From my experience, apache and jetty perform roughly
the same when serving static content. One of my pet peeves is setups
that jump through hoops to make some other app server serve static
content. Jetty does a fantastic job, and you shouldn't hesitate to
make it do anything if it'll make your life easier.
Dustin
On Tue, Jul 6, 2010 at 9:21 AM, Sander de
Groot <s.degroot@xxxxxx> wrote:
Currently
in our production system we use the well-known LAMP setup. Because of
internal reasons we've decided to move from LAMP to a setup with Java.
We're trying multiple kinds of setups one of which is: Apache as
Load-Balancer and static file server and an application container
(Jetty in this case).
We've decided that Apache should be in front of the application server
so Apache can provide us a load-balanced environment (with mod_proxy)
and vhosting. However, we are not sure how we'll be serving static
content.
While searching I've found that the separation of static and dynamic
content is fairly common. Apache (or another file server) is often used
as static content server while Java is only used for the dynamic stuff.
The problem however is that we've got lots of static content which is
not accessible for the public. (login/session required) If we'll be
using Apache for serving the static content then we're required to
create a module which connects to the application server for
authorization - since the application server is the one responsible for
handling auth etc.
Therefore we're considering to let Jetty do the file serving instead.
The only problem with this option is that we've no clue of the
performance versus Apache. Say we let Jetty serve all static files, how
will it perform against a simple Apache file server? Note that Apache
is still in front of the application server and Jetty will need to send
the result to apache which will forward the result to the browser.
(mod_proxy)
Some additional info:
- The server will be serving about 90 GB of static files
- 2.5 requests per second (peak 250 req/sec)
- about 600 vhosts (amount of handlers/servlets for Jetty)
- NFS for storage
/I'd be happy to provide some more info, just request (please be
specific)/
Can someone enlighten me on this subject?
Regards,
Sander
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users
|
