Re: High Load examples?
On 07.01.2010 12:24, Alexander Skwar wrote: Right now, we're using Bea WebLogic as our application server. We'd like to change to Tomcat 6. Now the creator of the application being run on the App Server said, that Tomcat works very well under low usage / low load situations. But if there are many (unsure about the definition of many...) users, Tomcat might tend to not perform so well anymore. I'd say that's a clear case of FUD [1]. Of course there will be performance differences between various implementations of the same spec and between different core architectures, but I can confirm that I know lots of applications that run in production on Tomcat with - more than 1.000 users logged in per instance (sessions) - more than 500 requests per second per instance - more than 100 concurrent requests I suppose many might mean like 50-100+ concurrent users using the App or system at the same time. Now I'm wondering, if that's actually true - does Tomcat not perform well anymore, if there are many users using it? Does anyone of you maybe have real world examples of high profile / high load sites using Tomcat (6)? I'm not allowed to disclose details, but examples are banking applications with multi million registered users, social networks again with mutli million registered users and very active ecommerce sites. There's lots of business critical and high load Tomcat deployment out there. But: in all cases I did performance troubleshooting the root cause was either in the web application or some outside component. Tomcat only limits what you can achieve and those limits are usually much higher than what you need. The amount of performance you really achieve at the end ist mostly limited by the web application itself. Regards, Rainer [1] http://en.wikipedia.org/wiki/Fear,_Uncertainty_and_Doubt - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
High Load examples?
Hello. Right now, we're using Bea WebLogic as our application server. We'd like to change to Tomcat 6. Now the creator of the application being run on the App Server said, that Tomcat works very well under low usage / low load situations. But if there are many (unsure about the definition of many...) users, Tomcat might tend to not perform so well anymore. I suppose many might mean like 50-100+ concurrent users using the App or system at the same time. Now I'm wondering, if that's actually true - does Tomcat not perform well anymore, if there are many users using it? Does anyone of you maybe have real world examples of high profile / high load sites using Tomcat (6)? Best regards, Alexander -- View this message in context: http://old.nabble.com/High-Load-examples--tp27058015p27058015.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: High Load examples?
2010/1/7 Alexander Skwar alexanders.mailinglists+nos...@gmail.com: Right now, we're using Bea WebLogic as our application server. We'd like to change to Tomcat 6. Now the creator of the application being run on the App Server said, that Tomcat works very well under low usage / low load situations. But if there are many (unsure about the definition of many...) users, Tomcat might tend to not perform so well anymore. I suppose many might mean like 50-100+ concurrent users using the App or system at the same time. Now I'm wondering, if that's actually true - does Tomcat not perform well anymore, if there are many users using it? Does anyone of you maybe have real world examples of high profile / high load sites using Tomcat (6)? University of Leeds routinely had 100+ active users on its Bodington VLE, and I'm aware of Sakai sites that load-balance across 4-8 Tomcat application servers that can serve around 5,000 concurrent users. A correctly configured Tomcat has no problem at high loads. It's barely possible your application creator might be talking in code for the following: Something in WebLogic means that our application runs fine, whereas something in Tomcat tickles a bug in our application that means it doesn't scale. This isn't unusual - unless an application is tested under many containers, it's very common for a platform dependence to creep in. - Peter - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: High Load examples?
On 07/01/2010 11:24, Alexander Skwar wrote: Hello. Right now, we're using Bea WebLogic as our application server. We'd like to change to Tomcat 6. Now the creator of the application being run on the App Server said, that Tomcat works very well under low usage / low load situations. But if there are many (unsure about the definition of many...) users, Tomcat might tend to not perform so well anymore. I suppose many might mean like 50-100+ concurrent users using the App or system at the same time. Now I'm wondering, if that's actually true - does Tomcat not perform well anymore, if there are many users using it? Does anyone of you maybe have real world examples of high profile / high load sites using Tomcat (6)? The powered by list [1] is a good place to start. The reference I usually use (because I work for SpringSource) is actually a tc Server reference [2] but all the stuff that matters (the nice things they say about increased throughput, lower server load and improved scalability) is pure Tomcat. In my experience if an app performs badly under load it doesn't matter what application server you run it on it will always perform badly under load. With well written applications I have seen a single Tomcat instance handle 1600 concurrent requests all with sub-second response time quite happily with 1GB RAM and ~5% CPU. In that case the load testing framework fell over long before Tomcat even looked like it might be struggling - but it was a *very* well written application. Equally, I have seen applications with issues struggle to manage 10 concurrent users. Keep in mind that you may need to tune threads, memory and GC settings to suit your app and the associated load. HTH, Mark [1] http://wiki.apache.org/tomcat/PoweredBy [2] http://www.springsource.com/files/uploads/all/pdf_files/customer/Associated%20Newspapers%20Case%20Study1.pdf - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: High Load examples?
of course there can't be a high-load thread without me, so here are my 2 cents: 2 cents I'm working in high-performance high-portal environment since 2004, and i must say that starting with tomcat 5 i've never experienced any performance problems caused by tomcat itself. The number of concurrent users and, more important, concurrent requests on a tomcat instance are limited by your network bandwidth, your cpu, your ram and, first of all, your application but not tomcat. My largest installation served more than 30.000 concurrent users, which produced about 4.000 requests per second (cumulated over few machines) all well under 500 ms delivery time. However the application was optimized for performance and scaleability. So, with 95% certainty your problem won't be tomcat! :-) Go for the kitty ;-) /2cents regards Leon - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: High Load examples?
+1 As usual it depends highly how well your app is written and where your bottleneck is. On a project, our very poorly-written Tomcat app was failing at ~50 concurrent users. BUT it was always because of the Oracle DB being starved on its 4 cores - 8GB of RAM machine. :-( On another project, we've written an app without any real concern for scalability at coding-time and it was easily able to accept ~2000 concurrent users on each of our 8 cores - 32GB of RAM machines on an ISP connection. It was more than asked, so we didn't try to benchmark the app more than that. But it was without any doubt and from the very beginning a better skilled team. So your mileage may vary and I'd advise to try and benchmark it using a load-testing tool. Regards, Pierre On Thu, Jan 7, 2010 at 9:40 PM, Leon Rosenberg rosenberg.l...@googlemail.com wrote: of course there can't be a high-load thread without me, so here are my 2 cents: 2 cents I'm working in high-performance high-portal environment since 2004, and i must say that starting with tomcat 5 i've never experienced any performance problems caused by tomcat itself. The number of concurrent users and, more important, concurrent requests on a tomcat instance are limited by your network bandwidth, your cpu, your ram and, first of all, your application but not tomcat. My largest installation served more than 30.000 concurrent users, which produced about 4.000 requests per second (cumulated over few machines) all well under 500 ms delivery time. However the application was optimized for performance and scaleability. So, with 95% certainty your problem won't be tomcat! :-) Go for the kitty ;-) /2cents regards Leon - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- Ad augusta per angusta Des résultats grandioses par des voies étroites
