Re: Configuration and performance questions
1. Yes of course. 4.1.30 is many release cycles ahead of 5.0.19. But that's a matter of course with all software. 2. Don't know. 3. I thought 'enterprise' was a marketing word ;) 4. Are you sure you've got apache configured correctly? I don't think there should be such a noticeable difference. Adam On 04/20/2004 03:07 AM Brian C. Dilley wrote: We are evaluating tomcat as a replacement for JRun. We are hoping that we can get some real world experiences in order to support our assumptions. We have the following questions and concerns regarding tomcat. 1. We are currently looking at version 5.0.19. Is there a performance\stability trade off compared to version 4.1.30? 2. What are the advantages or disadvantages of the different mod_jk2 worker types (ie: channelSocket, unixSocket, jni)? And are there any other connectors that we may want to evaluate. 3. Is there any documentation, or can anyone attest to the performance\stability of tomcat in an enterprise environment. 4. We have tested apache 2.0.49 using mod_jk2 (channel socket using AJP13) version 2.0.4 and tomcat 5.0.19 and found that it has some concurrency issues. Here are our findings, we are using siege for load testing: Config: Tomcat 5.0 / java 1.4.1 Concurrent: 100 Time: 5M Transactions: 3712 hits Availability: 100.00 % Elapsed time: 310.18 secs Data transferred: 171245696 bytes Response time: 7.80 secs Transaction rate: 11.97 trans/sec Throughput: 552084.94 bytes/sec Concurrency:93.37 Successful transactions:3712 Failed transactions: 0 Test Run 2 Config: Apache 2.0.49 / Tomcat 5.0 / mod_j2k / java 1.4.1 Concurrent: 100 Time: 5M Transactions: 750 hits Availability: 99.87 % Elapsed time: 1078.13 secs Data transferred: 6124581 bytes Response time: 27.71 secs Transaction rate: 0.70 trans/sec Throughput: 5680.74 bytes/sec Concurrency:19.27 Successful transactions: 747 Failed transactions: 4 Test Run 3 Config: Apache 1.3.27 / JRUN 3.0.2.1114 / mod_jrun / java 1.4.1 Concurrent: 100 Time: 5M Transactions: 3791 hits Availability: 100.00 % Elapsed time: 314.09 secs Data transferred: 62513590 bytes Response time: 7.34 secs Transaction rate: 12.07 trans/sec Throughput: 199030.83 bytes/sec Concurrency:88.62 Successful transactions:3791 Failed transactions: 0 Test Run 4 Config: Tomcat 5.0 / java 1.4.2_04 Transactions: 5176 hits Availability: 100.00 % Elapsed time: 304.94 secs Data transferred: 238784408 bytes Response time: 5.64 secs Transaction rate: 16.97 trans/sec Throughput: 783053.75 bytes/sec Concurrency:95.75 Successful transactions:5176 Failed transactions: 0 Test 5 Config: Apache 2.0.49 / Tomcat 5.0 / mod_j2k / java 1.4.2_04 Transactions: 701 hits Availability: 99.72 % Elapsed time: 659.95 secs Data transferred: 5580926 bytes Response time: 31.29 secs Transaction rate: 1.06 trans/sec Throughput: 8456.59 bytes/sec Concurrency:33.24 Successful transactions:679 Failed transactions:24 Test Run 6 Config: Apache 1.3.27 / JRUN 3.0.2.1114 / mod_jrun / java 1.4.2_04 Transactions: 3868 hits Availability: 100.00 % Elapsed time: 308.78 secs Data transferred: 63783320 bytes Response time: 7.16 secs Transaction rate: 12.53 trans/sec Throughput: 206565.58 bytes/sec Concurrency:89.68 Successful transactions:3868 Failed transactions:0 -- struts 1.2 + tomcat 5.0.19 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Configuration and performance questions
Brian, can you guys set up a web site with your results and configuration files. I would ask for you to post them but that is a lot for a mail list to handle. --Angus -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 3:29 AM To: Tomcat Users List Subject: Re: Configuration and performance questions 1. Yes of course. 4.1.30 is many release cycles ahead of 5.0.19. But that's a matter of course with all software. 2. Don't know. 3. I thought 'enterprise' was a marketing word ;) 4. Are you sure you've got apache configured correctly? I don't think there should be such a noticeable difference. Adam On 04/20/2004 03:07 AM Brian C. Dilley wrote: We are evaluating tomcat as a replacement for JRun. We are hoping that we can get some real world experiences in order to support our assumptions. We have the following questions and concerns regarding tomcat. 1. We are currently looking at version 5.0.19. Is there a performance\stability trade off compared to version 4.1.30? 2. What are the advantages or disadvantages of the different mod_jk2 worker types (ie: channelSocket, unixSocket, jni)? And are there any other connectors that we may want to evaluate. 3. Is there any documentation, or can anyone attest to the performance\stability of tomcat in an enterprise environment. 4. We have tested apache 2.0.49 using mod_jk2 (channel socket using AJP13) version 2.0.4 and tomcat 5.0.19 and found that it has some concurrency issues. Here are our findings, we are using siege for load testing: Config: Tomcat 5.0 / java 1.4.1 Concurrent: 100 Time: 5M Transactions: 3712 hits Availability: 100.00 % Elapsed time: 310.18 secs Data transferred: 171245696 bytes Response time: 7.80 secs Transaction rate: 11.97 trans/sec Throughput: 552084.94 bytes/sec Concurrency:93.37 Successful transactions:3712 Failed transactions: 0 Test Run 2 Config: Apache 2.0.49 / Tomcat 5.0 / mod_j2k / java 1.4.1 Concurrent: 100 Time: 5M Transactions: 750 hits Availability: 99.87 % Elapsed time: 1078.13 secs Data transferred: 6124581 bytes Response time: 27.71 secs Transaction rate: 0.70 trans/sec Throughput: 5680.74 bytes/sec Concurrency:19.27 Successful transactions: 747 Failed transactions: 4 Test Run 3 Config: Apache 1.3.27 / JRUN 3.0.2.1114 / mod_jrun / java 1.4.1 Concurrent: 100 Time: 5M Transactions: 3791 hits Availability: 100.00 % Elapsed time: 314.09 secs Data transferred: 62513590 bytes Response time: 7.34 secs Transaction rate: 12.07 trans/sec Throughput: 199030.83 bytes/sec Concurrency:88.62 Successful transactions:3791 Failed transactions: 0 Test Run 4 Config: Tomcat 5.0 / java 1.4.2_04 Transactions: 5176 hits Availability: 100.00 % Elapsed time: 304.94 secs Data transferred: 238784408 bytes Response time: 5.64 secs Transaction rate: 16.97 trans/sec Throughput: 783053.75 bytes/sec Concurrency:95.75 Successful transactions:5176 Failed transactions: 0 Test 5 Config: Apache 2.0.49 / Tomcat 5.0 / mod_j2k / java 1.4.2_04 Transactions: 701 hits Availability: 99.72 % Elapsed time: 659.95 secs Data transferred: 5580926 bytes Response time: 31.29 secs Transaction rate: 1.06 trans/sec Throughput: 8456.59 bytes/sec Concurrency:33.24 Successful transactions:679 Failed transactions:24 Test Run 6 Config: Apache 1.3.27 / JRUN 3.0.2.1114 / mod_jrun / java 1.4.2_04 Transactions: 3868 hits Availability: 100.00 % Elapsed time: 308.78 secs Data transferred: 63783320 bytes Response time: 7.16 secs Transaction rate: 12.53 trans/sec Throughput: 206565.58 bytes/sec Concurrency:89.68 Successful transactions:3868 Failed transactions:0 -- struts 1.2 + tomcat 5.0.19 + java
Configuration and performance questions
We are evaluating tomcat as a replacement for JRun. We are hoping that we can get some real world experiences in order to support our assumptions. We have the following questions and concerns regarding tomcat. 1. We are currently looking at version 5.0.19. Is there a performance\stability trade off compared to version 4.1.30? 2. What are the advantages or disadvantages of the different mod_jk2 worker types (ie: channelSocket, unixSocket, jni)? And are there any other connectors that we may want to evaluate. 3. Is there any documentation, or can anyone attest to the performance\stability of tomcat in an enterprise environment. 4. We have tested apache 2.0.49 using mod_jk2 (channel socket using AJP13) version 2.0.4 and tomcat 5.0.19 and found that it has some concurrency issues. Here are our findings, we are using siege for load testing: Config: Tomcat 5.0 / java 1.4.1 Concurrent: 100 Time: 5M Transactions: 3712 hits Availability: 100.00 % Elapsed time: 310.18 secs Data transferred: 171245696 bytes Response time: 7.80 secs Transaction rate: 11.97 trans/sec Throughput: 552084.94 bytes/sec Concurrency:93.37 Successful transactions:3712 Failed transactions: 0 Test Run 2 Config: Apache 2.0.49 / Tomcat 5.0 / mod_j2k / java 1.4.1 Concurrent: 100 Time: 5M Transactions: 750 hits Availability: 99.87 % Elapsed time: 1078.13 secs Data transferred: 6124581 bytes Response time: 27.71 secs Transaction rate: 0.70 trans/sec Throughput: 5680.74 bytes/sec Concurrency:19.27 Successful transactions: 747 Failed transactions: 4 Test Run 3 Config: Apache 1.3.27 / JRUN 3.0.2.1114 / mod_jrun / java 1.4.1 Concurrent: 100 Time: 5M Transactions: 3791 hits Availability: 100.00 % Elapsed time: 314.09 secs Data transferred: 62513590 bytes Response time: 7.34 secs Transaction rate: 12.07 trans/sec Throughput: 199030.83 bytes/sec Concurrency:88.62 Successful transactions:3791 Failed transactions: 0 Test Run 4 Config: Tomcat 5.0 / java 1.4.2_04 Transactions: 5176 hits Availability: 100.00 % Elapsed time: 304.94 secs Data transferred: 238784408 bytes Response time: 5.64 secs Transaction rate: 16.97 trans/sec Throughput: 783053.75 bytes/sec Concurrency:95.75 Successful transactions:5176 Failed transactions: 0 Test 5 Config: Apache 2.0.49 / Tomcat 5.0 / mod_j2k / java 1.4.2_04 Transactions: 701 hits Availability: 99.72 % Elapsed time: 659.95 secs Data transferred: 5580926 bytes Response time: 31.29 secs Transaction rate: 1.06 trans/sec Throughput: 8456.59 bytes/sec Concurrency:33.24 Successful transactions:679 Failed transactions:24 Test Run 6 Config: Apache 1.3.27 / JRUN 3.0.2.1114 / mod_jrun / java 1.4.2_04 Transactions: 3868 hits Availability: 100.00 % Elapsed time: 308.78 secs Data transferred: 63783320 bytes Response time: 7.16 secs Transaction rate: 12.53 trans/sec Throughput: 206565.58 bytes/sec Concurrency:89.68 Successful transactions:3868 Failed transactions:0 -- Brian C. Dilley [EMAIL PROTECTED] LowerMyBills.com
