« links for 2007-07-07 | Main | links for 2007-07-10 »


Adam Bien:

My yesterday entry "After one year Eclipse's abstinence, I had to close netbeans and use eclipse :-)" caused too much traffic and overtaxed my jboss server.Because of the high memory consumption the oom-killer terminated not only jboss, but also glassfish v2, james and my databases."

Weird. Adam's pages always seem to get served from origin; repeated requests for resources like CSS files will come back with 304 not modified (good), but not the main entry pages.

"Now I'm really motivated to speed-up the migration of the remaining applications from jboss to glassfish :-). The main reason for the migration from jboss to glassfish was the command-line interface as well as the great JSF based admin GUI and built-in monitoring (with graphical output...) capabilities. I'm curious whether Glassfish will be also killed by oom, or could handle the same load"

Investing in some time in cache configuration might pay off better than a new app server ;)

July 8, 2007 10:32 PM


Aristotle Pagaltzis
(July 9, 2007 03:29 AM #)

Parlez-vous ETag? :)

Adam Bien
(July 9, 2007 06:54 AM #)

You are partially right. But now run 2 server on my machine. If I kill one, I will get more ressources for the other. Because of admin capabilities I will use glassfish.

Caching works, because I use Apache in front. The caching of the content is the responsibility of the jroller - I will upgrade it next.

So I don't think, that caching is the issue....:-) But thank you for the post!

Mark Nottingham
(July 10, 2007 06:30 AM #)

Aristotle - ETags aren't the end-all in caching; in fact, they're probably the least useful part of HTTP, as far as caching goes.

If you have to use an ETag to validate, you can't avoid the roundtrip to the origin server, so your saving is only in transit, and *maybe* some CPU on the origin (although there are *very* few who take advantage of that).

Additionally, ETags cause many servers to trip up when using compression, causing interoperability issues with caches.

I'd take Last-Modified over ETags for most normal Web content; it's only when you're doing online editing that you really need them. Better yet, use Cache-Control.

(sorry if I'm venting, I just am sick of seeing ETags being used as a proxy for caching :)

Post a comment

(you may use HTML tags for style)

Remember Me?

Trackback Pings

TrackBack URL for this entry: