Hmm, I was using GET. Though I doubt that using POST would be different
(doPost() calls doGet()).
What are all of the JMeter components in your Thread Group? All I have are:
* HTTP Request Defaults
* HTTP Request (doe the single GET)
* Summary Report
The only other thing I can think of is that
Ran JMeter on my laptop (dual core AMD) and JBossAS on my desktop (quad core
Intel). Laptop showed about 70-80% CPU usage. Desktop barely registered 10%
usage. I was getting 333 requests/second. Hmm, that was using wireless on my
laptop. Turned off wireless and used a wired connection. Now my
Hi Peter - I'll try and answer all your Qs here :)
Post #1:
I have tried numerous thread group settings thus far - low numbers of threads
w/ many repetitions, high threads w/ many repetitions, various ramp-up times -
I still get a max of around 50 /s, be it when running JMeter on my windows
Are you running JBossAS on both Linux and WinXP? And getting the same results?
I assume your Linux is 64-bit (based on the heap settings used - 32-bit is
limited to around 2.7GB heaps on Linux and 1.5 on WinXP), am I correct? Which
distro?
Are you are running 64-bit WinXP? If only 32-bit, what
I am running JBoss solely on the Linux box. Any yes the linux is 64-bit CentOS.
Inspired by your Hello world test, I tried POSTing to a dummy servlet running
on a Tomcat server (on another machine) that simply prints the request to file
and returns. I can get the requests up to ~60/second, but
Thanks for your input.
For this particular test I was trying to overload the server with requests to
see if anything extremely bad happened. Is it reasonable to suppose that the
server isn't accepting/processing the HTTP requests because it is already so
loaded with work? Like you said, this
How many threads are you running in JMeter? Have you tried starting out with
only a few threads, and slowly increasing the number of threads, noting how the
system behaves for each run?
How many processors (or cores) are on the JBossAS box?
What Windows performance statistics are you
Which listener are you using?
Why do I ask? Well, I used the Summary Report listener. It said Throughput =
2.0/sec (running a single thread for 200 requests) and = 44.0/sec (running 10
threads for 200 requests). The problem is, my 1 thread run lasted less than 1
second, and the 10 thread run
Looks like if I want to take this any further I will have to put JMeter on
another machine. It is the one doing all of the processing and JBossAS is
hardly doing anything.
I am also seeing a lot of kernel time, which usually indicates GC processing.
At this time, I let everything run with
OK, if the JBossAS box is running at 85% CPU load, you now have to find the
bottleneck there and fix it.
I assume when you said earlier that this doesn't max out the server that you
consider 85% as not being maxed out. For an app server, actually, it is.
Realistically, you don't want to push
Is JMeter running on the same machine as JBossAS? Perhaps JMeter, or the
network connection between the JMeter machine and the JBossAS machine, is where
the problem is.
What processor utilization are you seeing?
View the original post :
Thanks for the response.
I have ran JMeter from 3 seperate machines (never the same machine as JBoss)
both seperately and simulataneously, all with the same cumulative thoroughput
of ~50 per second. This led me to believe that the the problem was on the JBoss
box.
The processor load is around
12 matches
Mail list logo