Load testing, benchmarking, and tuning 2007-08-07 - By rhull
Back
Hi,
I'm new to the forum, and I'm a little new to Tomcat load
testing/benchmarking. I've done some searching on the 'net, but I haven't
been able to turn up anything useful that addresses my issues. I'm hoping
somebody could provide some helpful thoughts.
I've got Tomcat (5.0) running on Linux with JVM 1.5.0_12, with a pretty thin
servlet. I'm fairly new to benchmarking/load testing with Tomcat, and some
of my numbers seem odd.
Load testing with WAPT from a Windows box across the internet to Tomcat
running on the Linux machine, I'm only seeing something around 15
transactions per second. This seems like an unlikely low number to me.
When I run load testing local to the Linux box using Siege, I'm seeing
around 600 transactions per second. This seems like an unrealistically
large number to me, and I assume the TCP/IP loopback is taking a lot of
network-related effort out of the equation.
I've tried fiddling with the server.xml thread settings, but it didn't seem
to have much affect on my transactions per second.
Running "top" on the box while the Siege load testing was occurring gave me
this information:
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
top - 08:49:01 up 60 days, 23:32, 2 users, load average: 3.34, 0.77, 0.33
Tasks: 148 total, 2 running, 146 sleeping, 0 stopped, 0 zombie
Cpu(s): 19.2% us, 71.0% sy, 0.0% ni, 9.8% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 8310224k total, 1227552k used, 7082672k free, 191868k buffers
Swap: 2096472k total, 0k used, 2096472k free, 612832k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
29503 tomcat 25 0 1356m 200m 13m S 711 2.5 41:05.61 java
15500 rhull 19 0 1030m 9124 892 S 10 0.1 0:02.23 siege
13772 rhull 15 0 10424 2060 1380 S 0 0.0 0:05.66 sshd
15603 rhull 16 0 3660 992 764 R 0 0.0 0:00.02 top
1 root 16 0 2020 548 468 S 0 0.0 0:03.50 init
2 root RT 0 0 0 0 S 0 0.0 0:00.25 migration/0
3 root 34 19 0 0 0 S 0 0.0 0:05.19 ksoftirqd/0
4 root RT 0 0 0 0 S 0 0.0 0:00.47 migration/1
5 root 34 19 0 0 0 S 0 0.0 0:00.27 ksoftirqd/1
6 root RT 0 0 0 0 S 0 0.0 0:00.18 migration/2
7 root 34 19 0 0 0 S 0 0.0 0:11.89 ksoftirqd/2
8 root RT 0 0 0 0 S 0 0.0 0:00.23 migration/3
9 root 34 19 0 0 0 S 0 0.0 0:00.02 ksoftirqd/3
10 root RT 0 0 0 0 S 0 0.0 0:00.27 migration/4
11 root 34 19 0 0 0 S 0 0.0 0:18.63 ksoftirqd/4
12 root RT 0 0 0 0 S 0 0.0 0:00.19 migration/5
13 root 34 19 0 0 0 S 0 0.0 0:00.05 ksoftirqd/5
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
There's obviously some load on the box (though not necessarily CPU), but it
certainly doesn't seem to be maxed out close to 100% of any resources.
So, I'm kind of stuck:
A) How can I determine what kind of ballpark, realistic transaction
throughput I *should* be expecting with my particular combination of
hardware and software?
B) How can I determine what the bottlenecking factor(s) is(are) on the
throughput?
--
View this message in context: http://www.nabble.com/Load-testing%2C
-benchmarking%2C-and-tuning-tf4229615.html#a12032715
Sent from the Tomcat - User mailing list archive at Nabble.com.
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
