Re: [Resin-interest] Compelling reasons to use Resin?
Scott: On Oct 17, 2007, at 6:25 AM, Jan Kriesten wrote: a recent comparison between resin 3.0.9 and tomcat 5.5.3 can be found here: http://raibledesigns.com/rd/entry/resin_slower_than_tomcat_fails on this comparison maybe scott could comment? It's not a useful benchmark. It measures startup time and JSP compilation time, not runtime. I'm actually embarrassed for the industry that Java people link to it as if it were a real benchmark. (That's not to say startup time isn't important, especially during development, but it's not a performance comparison.) Exactly my thought. I don't see any information about the number of concurrent threads, so unless this is implicit by some means out of my knowledge, this measures only a single request. Doesn't say much about how an appserver performs in a live environment. Most comparisons I've seen (years ago now) showed that which server performed best depends quite a bit on how much load (concurrent requests) it is under. Also, if you want to compare maximum performance you'd want to use Resins JNI features and make use of Resins fast JSTL. /Mattias ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Compelling reasons to use Resin?
hi, Exactly my thought. I don't see any information about the number of concurrent threads, so unless this is implicit by some means out of my knowledge, this measures only a single request. Doesn't say much about how an appserver performs in a live environment. Most comparisons I've seen (years ago now) showed that which server performed best depends quite a bit on how much load (concurrent requests) it is under. Also, if you want to compare maximum performance you'd want to use Resins JNI features and make use of Resins fast JSTL. fair enough! i agree this is not a valid and representative benchmark. but: people are reading those and especially people who decide things. regards, --- jan. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Compelling reasons to use Resin?
Jan: Exactly my thought. I don't see any information about the number of concurrent threads, so unless this is implicit by some means out of my knowledge, this measures only a single request. Doesn't say much about how an appserver performs in a live environment. Most comparisons I've seen (years ago now) showed that which server performed best depends quite a bit on how much load (concurrent requests) it is under. Also, if you want to compare maximum performance you'd want to use Resins JNI features and make use of Resins fast JSTL. fair enough! i agree this is not a valid and representative benchmark. but: people are reading those and especially people who decide things. :-( I thought I'd post a clarification on the blog, but it didn't work. Btw, here is a more recent comparison on the same blog: http://raibledesigns.com/rd/entry/comparing_open_source_application_servers Still just a single thread though, so still not a performance comparison. (And this time the author hints to be aware of that too) This time Resin (supposedly GPL) and Tomcat has about the same results (as do the others). ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Compelling reasons to use Resin?
hi hari, i have been using resin since early version 2 and haven't regret it. there are some cases which i'd say are compelling reasons to use it over tomcat, where you already brought up some yourself: To close, I should say that I personally love resin - its elegance, configuration simplicity and developer-friendliness. another compelling reason i see in your requirement specially as look to grow and add additional servers resin has an easy neat way to load-balance and easy session replication between it's instances. some things about resin aren't that good, of course, and should be addressed. for one the documentation - which never really was up-to-date nor showed more than a glimpse of resin's capabilities (example config-cases would be nice). also, there always have been problems resin being non-standard-compliant in some respect. a recent comparison between resin 3.0.9 and tomcat 5.5.3 can be found here: http://raibledesigns.com/rd/entry/resin_slower_than_tomcat_fails on this comparison maybe scott could comment? regards, --- jan. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Compelling reasons to use Resin?
We're listening to your feedback regarding documentation, and are in the process of improving it across the board, starting with Hessian. On Oct 17, 2007, at 7:25 AM, Jan Kriesten wrote: hi hari, i have been using resin since early version 2 and haven't regret it. there are some cases which i'd say are compelling reasons to use it over tomcat, where you already brought up some yourself: To close, I should say that I personally love resin - its elegance, configuration simplicity and developer-friendliness. another compelling reason i see in your requirement specially as look to grow and add additional servers resin has an easy neat way to load-balance and easy session replication between it's instances. some things about resin aren't that good, of course, and should be addressed. for one the documentation - which never really was up-to-date nor showed more than a glimpse of resin's capabilities (example config-cases would be nice). also, there always have been problems resin being non-standard- compliant in some respect. a recent comparison between resin 3.0.9 and tomcat 5.5.3 can be found here: http://raibledesigns.com/rd/entry/resin_slower_than_tomcat_fails on this comparison maybe scott could comment? regards, --- jan. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Compelling reasons to use Resin?
Greetings, I've been a Resin advocate for several years now. When I first did a performance comparison between Resin 2 and Tomcat, Resin's performance simply blew me away. Like many other people on this list, I imagine I switched entirely to recommending resin as the application server for all the projects I've worked on. They were all small startups so it didn't count towards hundreds of licenses, but still. Now, at another startup that I'm working with - with a licensed version of Resin Pro for our one app server -I'm being asked to justify the use of Resin over Tomcat, specially as look to grow and add additional servers. We use Resin only as a servlet container, so its EJB and PHP capabilities are not a justification. Googling around leads me to believe that Tomcat has gotten a lot faster recently, with NIO support in 6.0.x, and that the performance gap may have narrowed of late. So I seek the collective wisdom of the list: what are some of the compelling reasons that led you to choose Resin Pro over other application servers, and Tomcat in particular? Is anyone aware of recent benchmarks that compare resin and tomcat? To close, I should say that I personally love resin - its elegance, configuration simplicity and developer-friendliness. It's just that I'm trying to find a reason to convince management why we should use it over the free application server. Many thanks, - Hari ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
