Hello all,
In the goal of benchmarking the Snapshot release of jUDDI
(http://people.apache.org/repo/m2-snapshot-repository/org/apache/juddi/juddi-portal-bundle/3.0.0.SNAPSHOT/juddi-portal-bundle-3.0.0.20090723.201427-7.zip),
I tried to determine the rate at which businesses could be registered to
the node. Over several load test runs, I tried varying constant arrival
rates the highest of which was 7491 transactions/hour (so, publishing
7491 businesses per hour) which ran for 1h 42m 45s without any problems.
Higher rates of arrival made the system unresponsive after some time.
The time after which the system stopped responding varied with the load
that was put on the node, it would seem. The table below shows the the
arrival rate used for each run as well as it's duration, the reason the
test stopped, the rate achieved and a link to the XLT report for that run.
Date Scenario *Targeted* Arrival Rate Max Users Scheduled Length
Acual Length Reason for test stopping Comments Report
2009.08.03 TRegisterBusiness 5000t/h 20 72:00:00 63:21:02 Stopped
test manually after it had run all weekend. Achieved 5000 t/h without
error report
<http://xlt.xceptance.de/download/results/juddi/20090803-092925/>
2009.08.03 TRegisterBusiness 7000t/h 20 02:00:00 02:00:01 End of
run. Achieved 7000 t/h without error report
<http://xlt.xceptance.de/download/results/juddi/20090803-122920/>
2009.08.03 TRegisterBusiness 7500t/h 20 02:00:00 01:42:45 Stopped
manually to go to next run. Achieved 7491 t/h without error report
<http://xlt.xceptance.de/download/results/juddi/20090803-142345/>
2009.08.03 TRegisterBusiness 10000t/h 20 02:00:00 01:22:16 Stopped
manually to go to next run. Achieved 9969 t/h without error report
<http://xlt.xceptance.de/download/results/juddi/20090803-155147/>
2009.08.03 TRegisterBusiness 20000t/h 20 01:00:00 00:14:42 No new
iterations showing up, server seams to stop responding to all users.
Achieved 19,494 t/h, but stopped responding after 14mins report
<http://xlt.xceptance.de/download/results/juddi/20090803-161411/>
2009.08.03 TRegisterBusiness 15000t/h 20 01:00:00 00:26:17 No new
iterations showing up, server seams to stop responding to all users.
Achieved 14,726 t/h, but stopped responding after 26mins report
<http://xlt.xceptance.de/download/results/juddi/20090803-165945/>
2009.08.04 TRegisterBusiness 12500t/h 20 18:00:00 00:37:25 No new
iterations showing up, server seams to stop responding to all users.
Achieved 12,355 t/h, but stopped responding after 37mins report
<http://xlt.xceptance.de/download/results/juddi/20090804-090947/>
2009.08.04 TRegisterBusiness 11500t/h 20 18:00:00 00:54:32 No new
iterations showing up, server seams to stop responding to all users.
Achieved 11,382 t/h, but stopped responding after 54mins report
<http://xlt.xceptance.de/download/results/juddi/20090804-101452/>
2009.08.04 TRegisterBusiness 10500t/h 20 02:00:00 00:55:36 Max
errors were set to 1. An error occured while committing the
transaction. Achieved 10,493 t/h, but stopped responding after 55mins
because of single error. Must rerun test. report
<http://xlt.xceptance.de/download/results/juddi/20090804-111240/>
2009.08.04 TRegisterBusiness 10500t/h 20 04:00:00 00:58:42 Max
errors set to 1000. No new iterations showing up, server seams to stop
responding to all users. Achieved 10,483 t/h, but stopped responding
after 58mins. report
<http://xlt.xceptance.de/download/results/juddi/20090804-123327/>
2009.08.04 TRegisterBusiness 10000t/h 20 06:00:00 01:22:35 No new
iterations showing up, server seams to stop responding to all users.
Achieved 9,955 t/h, but stopped responding after 82mins. report
<http://xlt.xceptance.de/download/results/juddi//>
2009.08.04 TRegisterBusiness 25000t/h 20 01:00:00 00:04:41 No new
iterations showing up, server seams to stop responding to all users.
Achieved 21,613 t/h, but stopped responding after 4mins. This test was
run to get post hang up jstack outputs. report
<http://xlt.xceptance.de/download/results/juddi/20090804-163700/>
The TRegisterBusiness transaction consist of getting an AuthToken,
publishing a business, and publishing a random number of services
(between 1 and 7) under that business.
During the last run, I ran jstack three times minutes after the node had
stopped responding. The stack dumps can be found here:
http://xlt.xceptance.de/download/results/juddi/20090804-163700/jstackOutput_TRegisterBusiness_04.08.2009_01.txt
http://xlt.xceptance.de/download/results/juddi/20090804-163700/jstackOutput_TRegisterBusiness_04.08.2009_02.txt
http://xlt.xceptance.de/download/results/juddi/20090804-163700/jstackOutput_TRegisterBusiness_04.08.2009_03.txt
Next, I will switch to a mySQL DB and try to get some bench mark values
for it.
Jeremi
