[mapguide-users] Here's some stress testing on Mapguide

[Bruno Scott]

I've made some stress testing on Mapguide Enterprise 2010
(I will try the same test on MGOS 2.1)
I have a Dual core server 3.17 GHz with 4 gig of RAM
Running windows 2003 SP2 and IIS

I got a grinder script ( from Autodesk) that i have modifyed a little.
Test has been done using the ajaxviewer php and aspx
I've set grinder to simulate 20 concurent user repeating the same operations
This is the listof operation been repeating over and over by the 20 users
  1) Create a session + Sleep 2 sec
  2) Load the viewer + Sleep 2 sec
  3) Zoom + Sleep 2 sec
  4) Select one feature ( polygon based ) + Sleep 2 sec
  5) Clear selection + Sleep 2 sec
  6) Pan 3 times + Sleep 2 sec
  7) Zoom out  + sleep 2 sec

I have put some counter on the mapguide services and the iis(w3w) services
	mg net	w3w net	mg php	w3w php
1 min	64000k	58600k	64000k	45800k
2 min	72000k	63700k	64400k	51500k
3 min	68500k	67700k	69000k	65300k
4 min	71700k	71500k	71500k	68900k
5 min	72500k	76000k	73300k	72800k
6 min	77000k	77555k	77000k	76200k
7 min	82000k	81500k	80000k	80000k

http://n2.nabble.com/file/n3182666/Image1.gif 

Mapguide stopeed working after 35 minutes
there were still enough memory to run
mg was at 99000k
w3w was at 300000k

So analysing these numbers some question rises,
a) Why would iis loose 4 meg of ram every minutes?
b) Mapguide is still consuming 2 meg / minutes but i think will end by
reusing some of this ram, further test will try to demonstrate that.
c) What is the real cause of the crash? Is there too much session created in
a short period of time?

Bruno Scott 
still investigating :)




-- 
View this message in context: http://n2.nabble.com/Here%27s-some-stress-testing-on-Mapguide-tp3182666p3182666.html
Sent from the MapGuide Users mailing list archive at Nabble.com.