Hello Heikki,
After a set period of time that depends on the number of users, the testing tool shows that requests are being sent to GeoNetwork but no response is returned. The tool waits for a response from GN and after 120 seconds when it hasn’t received one, the tool kicks out an error. While the test is running, if I start a browser and attempt to access GeoNetwork like I would do so normally, the page just “sits there” and returns nothing. Eventually I may see an “internal server error.”
While the load test is being run, the testing tool reports on the script components that are being run along with the response times. For example, a simple search on “roads” may come back with a response time of .17 seconds, other times it might take 15 seconds.
Eventually, given enough time and/or users, all requests will time out.
We haven’t done any JVM profiling, though the CPUs on the server are maxed out. The JVM that GeoNetwork is running on locks up and has to be restarted; we think it’s running out of memory. Websphere has monitoring tools that we will try to utilize to help identify what is going on.
We are also storing session information into an Oracle table. If we don’t do this, because the sessions are so large, if we get enough users the JVM will run out of memory. This is a technique we’ve used with other applications with good success.
Regards, Bob
From: heikki [mailto:tropicano@…31…]
Sent: Tuesday, July 21, 2009 1:01 PM
To: Nutsch, Bob D.
Cc: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] Stress Testing / Load Testing
hi Bob,
could you provide more details on the nature of the problems that you get when going over those limits ?
Did you do any JVM profiling, or just test response times ?
Kind regards
Heikki Doeleman
On Tue, Jul 21, 2009 at 7:56 PM, Bob Nutsch <bnutsch@…273…> wrote:
Hello,
We’ve been running some load tests on GeoNetwork beginning with 2.2 and
currently with 2.4RC2. In those tests, and using LoadRunner, we’ve scripted
a number steps that a user might take. GeoNetwork is installed in our
Websphere infrastructure, and requests are going through a proxy server.
In all of our tests we hit a limit after which no further connections to GN
are allowed. It’s a cache issue of some type we believe, not a hard limit.
Though the server processors are very busy, the JVM does not crash. Before
there are problems, tt appears that we can have 15 concurrent users running
for 15 minutes, 10 users for 20 minutes, or 5 users for an unlimited (?)
time.
I’m curious if anyone else has seen anything similar and/or used testing
tools such as LoadRunner or WebLOAD? I’m also looking for any ideas on how
to improve performance.
Regards, Bob
–
View this message in context: http://n2.nabble.com/Stress-Testing—Load-Testing-tp3295190p3295190.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork