DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-11-09 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |




--- Additional Comments From [EMAIL PROTECTED]  2007-11-09 15:21 ---
Some new information on this issue, so I reopened it.  

The problem seems to relate to parsing the body content when the **Transfer-
Encoding: chunked** header is present.  It appears that the chunk length gets
corrupted under load and the client is unable to parse the chunk out of the 
response body.

When the NIO connector parameter **socket.appWriteBufSize** is set to a value 
larger than the total response body, the error condition does not occur.

One might succesfully argue that this is proper performance tuning.  The Tomcat 
documents point out that to scale a large number of long held connections, the 
buffer sizes may need to be less than the response body (the memory footprint 
would be quite large otherwise).

Could there be a race condition involving the response buffering code?  

I have confirmed this behavior on both JDKs 1.5 and 1.6 on both Windows 2003 
and Linux.




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-08-06 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||WORKSFORME




--- Additional Comments From [EMAIL PROTECTED]  2007-08-06 16:56 ---
I'm unable to reproduce the problem, and have to jump to the conclusion that the
problem lies within Windows 2000 and JDK 1.6

Please reopen if you are able to reproduce it on another platform/jdk combo

Filip

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-08-03 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002





--- Additional Comments From [EMAIL PROTECTED]  2007-08-03 09:19 ---
Created an attachment (id=20589)
 -- (http://issues.apache.org/bugzilla/attachment.cgi?id=20589action=view)
Response generator servlet


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-08-03 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002





--- Additional Comments From [EMAIL PROTECTED]  2007-08-03 07:40 ---
Can you please try with 6.0.14, numerous bug fixes since .13
http://people.apache.org/~remm/tomcat-6/v6.0.14/

also, don't use direct buffers, there is a good chance the system is faster
without .

early next week I will examine your test cases
Filip

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-08-03 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002





--- Additional Comments From [EMAIL PROTECTED]  2007-08-03 18:08 ---
Hi Filip,
 I upgraded to JDK 1.6.0_02 and reran the tests with virtually the same 
results.   Rats!!!

Let me know if there is anything else I can do.

Guy



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-08-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002





--- Additional Comments From [EMAIL PROTECTED]  2007-08-02 11:43 ---
Created an attachment (id=20581)
 -- (http://issues.apache.org/bugzilla/attachment.cgi?id=20581action=view)
JSP That renerates a variable response buffer with configurable sleep delays


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-08-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002





--- Additional Comments From [EMAIL PROTECTED]  2007-08-02 11:44 ---
Created an attachment (id=20582)
 -- (http://issues.apache.org/bugzilla/attachment.cgi?id=20582action=view)
Grinder config file for load test


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-08-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002





--- Additional Comments From [EMAIL PROTECTED]  2007-08-02 11:46 ---
Created an attachment (id=20583)
 -- (http://issues.apache.org/bugzilla/attachment.cgi?id=20583action=view)
Grinder/JPython script that calls response generator JSP for 


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-08-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002





--- Additional Comments From [EMAIL PROTECTED]  2007-08-02 11:53 ---
I've added a simple JSP page to help work the issue.  

The Grinder load test scripts are now separate attachments.

The JSP page is pretty simplistic and I had to push the server hard.   It 
appears that the Content-Length header does not match the response buffer size.

During one of the test runs I got the following exeception in the system logs, 
although it seemed to be an isolated occurance.

===
2007-08-01 17:09:20,364 [http-8080-exec-9] ERROR 
org.apache.catalina.connector.CoyoteAdapter - An exception or error occurred in 
the container during the request processing
java.nio.BufferOverflowException
at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:311)
at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:290)
at sun.nio.ch.IOUtil.write(IOUtil.java:70)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at org.apache.tomcat.util.net.NioChannel.write(NioChannel.java:111)
at org.apache.tomcat.util.net.NioBlockingSelector.write
(NioBlockingSelector.java:57)
at org.apache.tomcat.util.net.NioSelectorPool.write
(NioSelectorPool.java:135)
at org.apache.tomcat.util.net.NioSelectorPool.write
(NioSelectorPool.java:130)
at org.apache.coyote.http11.InternalNioOutputBuffer.writeToSocket
(InternalNioOutputBuffer.java:433)
at org.apache.coyote.http11.InternalNioOutputBuffer.flushBuffer
(InternalNioOutputBuffer.java:761)
at org.apache.coyote.http11.InternalNioOutputBuffer.endRequest
(InternalNioOutputBuffer.java:398)
at org.apache.coyote.http11.Http11NioProcessor.action
(Http11NioProcessor.java:1089)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.coyote.Response.finish(Response.java:305)
at org.apache.catalina.connector.OutputBuffer.close
(OutputBuffer.java:276)
at org.apache.catalina.connector.Response.finishResponse
(Response.java:486)
at org.apache.catalina.connector.CoyoteAdapter.service
(CoyoteAdapter.java:285)
at org.apache.coyote.http11.Http11NioProcessor.process
(Http11NioProcessor.java:896)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process
(Http11NioProtocol.java:705)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run
(NioEndpoint.java:2049)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
2007-08-01 17:09:56,255 [http-8080-exec-11] ERROR 
org.apache.catalina.connector.CoyoteAdapter - An exception or error occurred in 
the container during the request processing
java.nio.BufferOverflowException
at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:311)
at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:290)
at sun.nio.ch.IOUtil.write(IOUtil.java:70)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at org.apache.tomcat.util.net.NioChannel.write(NioChannel.java:111)
at org.apache.tomcat.util.net.NioBlockingSelector.write
(NioBlockingSelector.java:57)
at org.apache.tomcat.util.net.NioSelectorPool.write
(NioSelectorPool.java:135)
at org.apache.tomcat.util.net.NioSelectorPool.write
(NioSelectorPool.java:130)
at org.apache.coyote.http11.InternalNioOutputBuffer.writeToSocket
(InternalNioOutputBuffer.java:433)
at org.apache.coyote.http11.InternalNioOutputBuffer.flushBuffer
(InternalNioOutputBuffer.java:761)
at org.apache.coyote.http11.InternalNioOutputBuffer.endRequest
(InternalNioOutputBuffer.java:398)
at org.apache.coyote.http11.Http11NioProcessor.action
(Http11NioProcessor.java:1089)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.coyote.Response.finish(Response.java:305)
at org.apache.catalina.connector.OutputBuffer.close
(OutputBuffer.java:276)
at org.apache.catalina.connector.Response.finishResponse
(Response.java:486)
at org.apache.catalina.connector.CoyoteAdapter.service
(CoyoteAdapter.java:285)
at org.apache.coyote.http11.Http11NioProcessor.process
(Http11NioProcessor.java:896)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process
(Http11NioProtocol.java:705)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run
(NioEndpoint.java:2049)
at 

DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-08-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002





--- Additional Comments From [EMAIL PROTECTED]  2007-08-02 16:48 ---
Update.I wrote a simple response generator servlet and re-ran the tests.   
Now performance on 6.0.13 is significantly *FASTER*.  However, I'm seeing a 
fair number of HTTPClient errors from Grinder as well as consistent buffer 
overflow exceptions.  This leads me to believe that the bottleneck has now 
shifted to the application code.

I've attached the test servlet.   Here are the stack traces:

===
Java exception whilst invoking test runner
File /apps/grinder-3.0/projects/TeaBenchmark/smallest-servlet-
400rps.py, line 40, in __call__
Caused by: java.io.IOException: HTTPClient.ParseException: Didn't find valid 
chunk length: 
at HTTPClient.StreamDemultiplexor.read(StreamDemultiplexor.java:372)
at HTTPClient.RespInputStream.read(RespInputStream.java:155)
at HTTPClient.HTTPResponse.readResponseData(HTTPResponse.java:1011)
at HTTPClient.HTTPResponse.getData(HTTPResponse.java:515)
at net.grinder.plugin.http.HTTPRequest$AbstractRequest.getHTTPResponse
(HTTPRequest.java:888)
at net.grinder.plugin.http.HTTPRequest.GET(HTTPRequest.java:385)
at net.grinder.plugin.http.HTTPRequest.GET(HTTPRequest.java:360)
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)


TOMCAT LOG STACK TRACE FOLLOWS:

2007-08-02 15:44:04,453 [http-8080-exec-17] ERROR 
org.apache.catalina.connector.CoyoteAdapter - An exception or error occurred in 
the container during the request processing
java.nio.BufferOverflowException
at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:311)
at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:290)
at sun.nio.ch.IOUtil.write(IOUtil.java:70)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at org.apache.tomcat.util.net.NioChannel.write(NioChannel.java:111)
at org.apache.tomcat.util.net.NioBlockingSelector.write
(NioBlockingSelector.java:57)
at org.apache.tomcat.util.net.NioSelectorPool.write
(NioSelectorPool.java:135)
at org.apache.tomcat.util.net.NioSelectorPool.write
(NioSelectorPool.java:130)
at org.apache.coyote.http11.InternalNioOutputBuffer.writeToSocket
(InternalNioOutputBuffer.java:433)
at org.apache.coyote.http11.InternalNioOutputBuffer.flushBuffer
(InternalNioOutputBuffer.java:761)
at org.apache.coyote.http11.InternalNioOutputBuffer.endRequest
(InternalNioOutputBuffer.java:398)
at org.apache.coyote.http11.Http11NioProcessor.action
(Http11NioProcessor.java:1089)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.coyote.Response.finish(Response.java:305)
at org.apache.catalina.connector.OutputBuffer.close
(OutputBuffer.java:276)
at org.apache.catalina.connector.Response.finishResponse
(Response.java:486)
at org.apache.catalina.connector.CoyoteAdapter.service
(CoyoteAdapter.java:285)
at org.apache.coyote.http11.Http11NioProcessor.process
(Http11NioProcessor.java:896)
at 
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process
(Http11NioProtocol.java:705)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run
(NioEndpoint.java:2049)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
2007-08-02 15:45:24,687 [http-8080-exec-11] ERROR 
org.apache.catalina.connector.CoyoteAdapter - An exception or error occurred in 
the container during the request processing
java.nio.BufferOverflowException
at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:311)
at java.nio.DirectByteBuffer.put(DirectByteBuffer.java:290)
at sun.nio.ch.IOUtil.write(IOUtil.java:70)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at org.apache.tomcat.util.net.NioChannel.write(NioChannel.java:111)
at org.apache.tomcat.util.net.NioBlockingSelector.write
(NioBlockingSelector.java:57)
at org.apache.tomcat.util.net.NioSelectorPool.write
(NioSelectorPool.java:135)
at 

DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-07-31 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |NEEDINFO




--- Additional Comments From [EMAIL PROTECTED]  2007-07-31 06:43 ---
There was a memory leak in 6.0.10 when using a dynamically sized thread pool.
The fix for this was to add a bounded pool of objects, and that will slow it
down a bit.
If you are up for it, please leave us your test case, with results from .10 and
.13 and I will see if there is anything else that happened.

thanks
Filip

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-07-31 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEEDINFO|ASSIGNED




--- Additional Comments From [EMAIL PROTECTED]  2007-07-31 09:04 ---
One thing I didn't mention is that I have 120 users configured in Grinder.   
The degradation was not small it was in excess of 50% making 6.0.13 unusable 
for us.   Also, under load EOFExceptions were occurring.   The application used 
for testing is quite ordinary and it would be difficult to provide.  I suspect 
that any one of the sample apps will work.

Steps to reproduce:
1) Set up a grinder test against a simple app like say the struts-mailreader.
2) Use JDK 1.6.0_01
3) Configure 120 concurrent users in Grinder.

Perform the tests on both 6.0.10 and 6.0.13.  Compare the requests/second 
throughput.

 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-07-31 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|ASSIGNED|NEEDINFO




--- Additional Comments From [EMAIL PROTECTED]  2007-07-31 10:15 ---
you need to provide more info, what are you testing, static files, size of the
files, JSP pages,
number of requests, sleeping between requests, etc

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 43002] - NIO connector performance issue in 6.0.13

2007-07-31 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=43002.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43002


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEEDINFO|ASSIGNED




--- Additional Comments From [EMAIL PROTECTED]  2007-07-31 10:48 ---
The response payload is about ~10K with JSP's that call Java application code.  
Normal unladen execution times are about ~8ms.   The web pages include one or 
more images/flash applications.   The test client ignores these however.  There 
are NO SLEEPS between requests, as we are trying to similate normal traffic 
through our load balancing appliances.   I'm attaching the grinder config file 
and JPython test script.

Here is the grinder configuration file:

# grinder configuration

# Required fields #
PROJECT=RefAppLoadTest

#TEST_SCRIPT=ReferenceAppTest_S9_DualNic_noimages_random_nosleep.py
#TEST_SCRIPT=ReferenceAppTest_noimages_random_nosleep.py
TEST_SCRIPT=ReferenceAppTest_DefaultContext_Random_NoSleep.py
#TEST_SCRIPT=ReferenceAppTest_noimages_nosleep_spiking.py
#TEST_SCRIPT=ReferenceAppTest_DefaultContext_Random_20RPS_rhvm2-3-4.py
#TEST_SCRIPT=ReferenceAppTest_DefaultContext_Random_TestResults1field_5RPS.py

# Duration of the full test (minutes)
# This time must match the time required for the test script
# to run
TEST_DURATION=10
#TEST_RUNS=2

# The users will be evenly distributed across all clients,
# using the floor of NUM_USERS/LOAD_CLIENTS
LINUX_LOAD_CLIENTS=sedplatfc5,sedplatfc3,sedplatfc4
#LINUX_LOAD_CLIENTS=sedplatfc5
WIN_LOAD_CLIENTS=

# Total number of users across all load clients
NUM_USERS=120

# Number of users to start with each grouping
USERS_IN_GROUP=30

# Time in seconds between the start of each group of users
GROUP_RAMPUP_TIME=120

# Total number of spike users
SPIKE=0

# How long between spikes in seconds
SPIKE_INTERVAL=180

# Deviation around the spike in milliseconds
SPIKE_SIGMA=750

# The server to test
# Barista sedplat9
#TARGET_SERVER=sedplat9:9100

# Tomcat sedplat9
#TARGET_SERVER=sedplat9:9000

# Tomcat sedplat3
#TARGET_SERVER=sedplat3:9000
#TARGET_SERVER=sedplat4:9000

#Tomcat on Red Hat
#TARGET_SERVER=sedplatfc1:9000

#Tomcat on Red Hat Virtual
TARGET_SERVER=sedplat9.go.com:9000

#Stouted Ref App
#TARGET_SERVER=sedplat5

#Quantified Stouted Advarked Ref App
#TARGET_SERVER=sedplat8:8082

# The process to monitor on the server
#TARGET_PROCESS=DPReferenceAppB
TARGET_PROCESS=DPReferenceApp.
#TARGET_PROCESS=inetinfo

# The interval to retrieve performance data samples from the server (seconds)
SAMPLING_PERIOD=5



# Optional fields #
# Defaults to no perfmon logging
#PERFMON=true

# Defaults to true
USE_CONSOLE=true

Here is the Python script
=
# The Grinder 3.0-beta30
# HTTP script recorded by TCPProxy at Sep 28, 2006 3:16:38 PM
import random

from net.grinder.script import Test
from net.grinder.script.Grinder import grinder
from net.grinder.plugin.http import HTTPPluginControl, HTTPRequest
from HTTPClient import NVPair
connectionDefaults = HTTPPluginControl.getConnectionDefaults()
httpUtilities = HTTPPluginControl.getHTTPUtilities()

requestsPerSecond = 50

# To use a proxy server, uncomment the next line and set the host and port.
# connectionDefaults.setProxyServer(localhost, 8001)

# These definitions at the top level of the file are evaluated once,
# when the worker process is started.

connectionDefaults.defaultHeaders = \
  ( NVPair('User-Agent', 'Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; 
rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7'),
NVPair('Accept-Encoding', 'gzip,deflate'),
NVPair('Accept-Language', 'en-us,en;q=0.5'),
NVPair('Accept-Charset', 'ISO-8859-1,utf-8;q=0.7,*;q=0.7'),
NVPair('INLINEREPLACE', 'Yes'), )

headers= \
  ( NVPair
('Accept', 'text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/
plain;q=0.8,image/png,*/*;q=0.5'),
NVPair
('Referer', 'http://sedplat9.go.com:9000/ReferenceApplication/ReferenceApplicati
on/dynamic/homePage'), )

url0 = 'http://sedplat9.go.com:9000'

articleIds = ['36', '113', '114', '115', '116', '117', '118', '119', '120', 
  '121', '122', '123', '124', '125', '126', '127', '128', '129', '13
0', '132', '622']

aboutIds = ['314','315','316','317','318', '319', '320', '321', '621']

# Create an HTTPRequest for each request, then replace the
# reference to the HTTPRequest with an instrumented version.
# You can access the unadorned instance using request101.__target__.
homePageRequest = HTTPRequest(url=url0, headers=headers)