RE: Throughput and scalability
Hey Peter - Where can I get the articles - are they in the FAQ or the archive somewhere. Any keywords you can suggest? -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 5:59 PM To: Tomcat Users List Subject: Re: Throughput and scalability if you're talking about XML transformation, the biggest factor is the parser you use and the cpu speed. If you read my old performance article on the resource page, you can see some old numbers for AMD 2ghz system. depending on how much XML you need to handle concurrently, you may want to consider XML accelerators to get near wire speed. The primary limitations for XML processing is CPU and RAM. hope that helps peter On Wed, 23 Feb 2005 14:25:32 -0800, Ross Poppel [EMAIL PROTECTED] wrote: Hi Tomcat Users - We are implementing Tomcat (with Axis) for HTML translation to a proprietary format (as a pass-thru). This is for submission to an external system (its pretty simple data) and back again. We were wondering if anyone has any ideas how you would size a box (Solaris/HP-UX based) if you want to get a specific throughput (x number of messages per second). Is there any guidelines anyone can recommend? --- Ross Poppel - [EMAIL PROTECTED] Solutions Architect, PORTAL Software Cell: (609) 744-2050 EFax: (617) 344-2585 SMS: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Throughput and scalability
It sounds like you are writing your own Business Integration Engine Ross, sometimes referred to as Enterprise Service Buses. They just take requests in 1 format, translate them to another format and pass them along - potentially splitting off actions and conditionally passing the request to multiple services. They are designed and optimized for those tasks. I believe there are several open source projects for this and I think they use Tomcat: http://bie.sourceforge.net/ http://activemq.codehaus.org/ http://www.openadaptor.org/ There are also several commercial ESB's- some designed for high scalability and redundancy, but they are pricey. Maybe these are overkill for what you are doing, but I suggest having a look at them before rolling your own. Byron -Original Message- From: Ross Poppel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 24, 2005 10:18 AM To: Tomcat Users List; Peter Lin Subject: RE: Throughput and scalability Hey Peter - Where can I get the articles - are they in the FAQ or the archive somewhere. Any keywords you can suggest? -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 5:59 PM To: Tomcat Users List Subject: Re: Throughput and scalability if you're talking about XML transformation, the biggest factor is the parser you use and the cpu speed. If you read my old performance article on the resource page, you can see some old numbers for AMD 2ghz system. depending on how much XML you need to handle concurrently, you may want to consider XML accelerators to get near wire speed. The primary limitations for XML processing is CPU and RAM. hope that helps peter On Wed, 23 Feb 2005 14:25:32 -0800, Ross Poppel [EMAIL PROTECTED] wrote: Hi Tomcat Users - We are implementing Tomcat (with Axis) for HTML translation to a proprietary format (as a pass-thru). This is for submission to an external system (its pretty simple data) and back again. We were wondering if anyone has any ideas how you would size a box (Solaris/HP-UX based) if you want to get a specific throughput (x number of messages per second). Is there any guidelines anyone can recommend? --- Ross Poppel - [EMAIL PROTECTED] Solutions Architect, PORTAL Software Cell: (609) 744-2050 EFax: (617) 344-2585 SMS: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Throughput and scalability
Hi Tomcat Users - We are implementing Tomcat (with Axis) for HTML translation to a proprietary format (as a pass-thru). This is for submission to an external system (its pretty simple data) and back again. We were wondering if anyone has any ideas how you would size a box (Solaris/HP-UX based) if you want to get a specific throughput (x number of messages per second). Is there any guidelines anyone can recommend? --- Ross Poppel - [EMAIL PROTECTED] Solutions Architect, PORTAL Software Cell: (609) 744-2050 EFax: (617) 344-2585 SMS: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Throughput and scalability
I do not think that anyone can answer that but you. It is so application specific that any answers we give would be SWAGs at best. Larry On Wed, 23 Feb 2005 14:25:32 -0800, Ross Poppel [EMAIL PROTECTED] wrote: Hi Tomcat Users - We are implementing Tomcat (with Axis) for HTML translation to a proprietary format (as a pass-thru). This is for submission to an external system (its pretty simple data) and back again. We were wondering if anyone has any ideas how you would size a box (Solaris/HP-UX based) if you want to get a specific throughput (x number of messages per second). Is there any guidelines anyone can recommend? --- Ross Poppel - [EMAIL PROTECTED] Solutions Architect, PORTAL Software Cell: (609) 744-2050 EFax: (617) 344-2585 SMS: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] Throughput and scalability
Ross, I recommend that you think along the lines of expandability. That is, a load balancer in front of tomcat(s) running on one or more servers. As demand increases you add more instances, then another server. There is also the nature of the communication with the external system to consider. It sounds like you should profile the app at a range of loads, identify bottlenecks, and design/specify accordingly. -Robert Larry Meadors wrote: I do not think that anyone can answer that but you. It is so application specific that any answers we give would be SWAGs at best. Larry On Wed, 23 Feb 2005 14:25:32 -0800, Ross Poppel [EMAIL PROTECTED] wrote: Hi Tomcat Users - We are implementing Tomcat (with Axis) for HTML translation to a proprietary format (as a pass-thru). This is for submission to an external system (its pretty simple data) and back again. We were wondering if anyone has any ideas how you would size a box (Solaris/HP-UX based) if you want to get a specific throughput (x number of messages per second). Is there any guidelines anyone can recommend? --- Ross Poppel - [EMAIL PROTECTED] Solutions Architect, PORTAL Software Cell: (609) 744-2050 EFax: (617) 344-2585 SMS: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Throughput and scalability
if you're talking about XML transformation, the biggest factor is the parser you use and the cpu speed. If you read my old performance article on the resource page, you can see some old numbers for AMD 2ghz system. depending on how much XML you need to handle concurrently, you may want to consider XML accelerators to get near wire speed. The primary limitations for XML processing is CPU and RAM. hope that helps peter On Wed, 23 Feb 2005 14:25:32 -0800, Ross Poppel [EMAIL PROTECTED] wrote: Hi Tomcat Users - We are implementing Tomcat (with Axis) for HTML translation to a proprietary format (as a pass-thru). This is for submission to an external system (its pretty simple data) and back again. We were wondering if anyone has any ideas how you would size a box (Solaris/HP-UX based) if you want to get a specific throughput (x number of messages per second). Is there any guidelines anyone can recommend? --- Ross Poppel - [EMAIL PROTECTED] Solutions Architect, PORTAL Software Cell: (609) 744-2050 EFax: (617) 344-2585 SMS: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
