Hey,

Thanks for your quick reply! Once a user logs in, he sends a constant rate
of presence and IM to the presense server in a infinite loop. In order to
keep sending Presence and IM he will need to stay logged in for the duration
of the test. So in answer to your question, I don't log out and users and
their tasks never finish [until of course the test is ended manually].

Is it better to use a higher heap size? Can this cause any negaitive
effects?



Deepak Brijnandan Goel wrote:
> 
> Hey
> 
> Namaskara~Nalama~Guten Tag
> 
> You might like to check for memory leaks in the application. Are your
> users
> logging out after finishing their task?
> 
> You might also like to increase your max heap size to 1 GB.
> 
> Deepak
>   --
> Keigu
> 
> Deepak
> +91-9765089593
> [email protected]
> 
> Skype: thumsupdeicool
> Google talk: deicool
> Blog: http://loveandfearless.wordpress.com
> Facebook: http://www.facebook.com/deicool
> 
> Check out my Work at:
> LinkedIn: http://in.linkedin.com/in/thumsupdeicool
> 
> "Contribute to the world, environment and more :
> http://www.gridrepublic.org
> "
> 
> 
> On Fri, Jun 4, 2010 at 4:35 PM, frogg6 <[email protected]> wrote:
> 
>>
>> I am using Jmeter to generate BOSH login, IM & Presence traffic to my
>> presence server. The test is for 5000 users and the traffic from jmeter
>> runs
>> through a proxy server before going to the presence server. I have setup
>> JMeter on 2 servers running 2 identical instances of my test scripts on
>> each
>> [2 x 2 x 1250 users/script = 5000 users]. The login period for 5000 uers
>> is
>> 20 mins after which time each user generates IM and Presence requests to
>> the
>> presence server. Everything is fine for the first 24 hours, I see a nice
>> steady CPU rate of around 60 % on my presence server. However after 24
>> hours
>> the CPU gradually gets larger and larger until the presence server's CPU
>> reaches about 90% which is a test failure. I have checked my presence
>> server
>> logs and everything looks fine so the problem must lie with the
>> toolboxes.
>> Any idea what might be causing the CPU to rise gradually after 24 hours?
>> Are
>> there any memory configurations etc that need to be set prior to running
>> a
>> test? I am using a HeapSize of min: 256, max: 512 which for each
>> instance.
>> Do the NewSize values have to match these in terms of ratio? My toolboxes
>> also contain 4 processors so I am tying each jmeter instance to a
>> separate
>> processor which seems to fix the problem intermittently. Any help would
>> be
>> much appreciated :-)
>> --
>> View this message in context:
>> http://old.nabble.com/Increasing-CPU-during-BOSH-Test-using-JMETER-tp28778525p28778525.html
>> Sent from the JMeter - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Increasing-CPU-during-BOSH-Test-using-JMETER-tp28778525p28778903.html
Sent from the JMeter - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to