I'm wondering if anyone has done some more recent work with 4.1.24 and more recent versions of other containers? I've been trying to google for benchmarks. Yes i know, benchmarks are a dime a dozen and I *should* just do my own. But I'm just not sure how to do so, and I'm fairly convinced I would "do it wrong." And also, there's a fair amount of logic in running the same benchmark against various versions. If someone could just convince a previous benchmarker to re-run their old code on newer versions....
So I'm asking publicly... has anyone done some benchmarking of Resin v. Tomcat lately ? And do you have results from a previous benchmark to compare against?
Also.. I'm not sure what everyone is complaining about Tomcat documentation for. I think it's pretty good (with the *notable* exception of mod_jk / WARP). I've downloaded Resin and don't find it's documentation clearly superior to Tomcat's.
As a side note for those unfamiliar, Mike Cannon-Brookes is a pretty well-informed guy and without trying to do a big PR job for him, his software www.atlassian.com/jira is very cool. [ April 29, 2003: Message edited by: Mike Curwen ]
OK, Ill be the first fool to jump into what is bound to become a sreaming firefight here. I have some VERY strong opinions on this subject but will try "to keep my big mouth shut" or at least tame. I also have to prefice this by saying I ONLY do servlet work...never had the use for JSP's so I cant comment there. Ive been developing on both containers for 2 years now... Tomcat fot customers websites (cheap hosting) & Resin on a full blown intranet web application.. Oh & I also used Resin on a rather large adult site I built for a company some years ago...no comments ... I dont usually deal with them but it paid the bills at the time! Here's my thoughts: Ease of setup: The resin.conf is so easy a trained chimp could set it up, finely commented, clear & consise. Tomcat? Oh god lets not even go there, as any "new entry" will tell you its just freaking painful to figure out the server.xml & web.xml the first time. I will say once you have figured it out it's OK but no where near as easy as Resin's. Support... I have never even attempted any support from jakarta because I have been told by many friends that it doesnt exist. On the flip side I had a problem with a version of resin, picked up the phone & called sales. Once I had explained my problem the gentleman said "Let me put you on the phone with our head programmer" You could have knocked me over with a feather. After a 5 minute talk with him & 2 emails that day we concluded a real bug had been found & they had a new version out in days...not months! I have since spoken to them again about pricing (ther lisence is a little sketchy) & asked why they didnt have a "one site setup price", only a full server price. The man said "Great idea" How does $100 a site sound WITH SUPPORT! Now to what the real question is... speed & reliability. Speed: Anyone who has ever tested the two side by side can VISUALLY see the difference. I recently loaded Tomcat 4x on my laptop. This pig sucked up so much ram the stupid thing could barely open the browser...now come on, the container isnt supposed to suck up more ram that the app! I went back to 3.2.2 & things were back to normal but there is still no way tomcat serves up pages faster than Resin with less of a footprint on the server. You dont need a test beside your own eyes. Reliability: Our large intranet app has been running Resin 2.1.4 wihout so much a whimper for 12 months. This app imports 10,000 + rows (200 columns) of comma deliminted input, parses it, inserts it into a db & then starts spitting out pdf files file a mad toaster, all the while serving up app pages to the employees. Not once have a been asked to "restart" it. My favorite story about Resin is the night I got locked out of the adult server I had to work on (via telnet) & had to update the resin.conf. It was 2 am on a sunday, the changes HAD to be made NOW & there was no one to call. I figured I was stuck so I just uploaded the new resin.conf via ftp without first stopping the engine. I was amazed when the container threw ONE xml parser exception, restarted & picked up the changes in seconds!... ON THE OTHER HAND, most Tomcat installations I have seen STILL cant automatically reload class files when they change without a restart. I had Tomcat freak out yesterday & go into an endless loop because the customer had a background image in her html along with one in the css body tag. Everytime a page would load with this mistake tomcat would go into an endless loop of illegalStateException - current state: flushing new state - coding. It would literally go forever until the machine locked up or a stop command was issued (actually a cntrl c) Thank heavens it was on my developer machine & not a server! Im sorry these people at caucho are building a better mousetrap & they CARE about their product. I was told flat out by their staff "we are here to help the developer" They are open to ideas & the input of the people who use their product every day. Jakarta seems to have lost their way...honestly I think they have "bit off more than they can chew" TOO Many products...not enough testing before release...starting to remind me of a certain "other" company that starts with M.