• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WO and Memory Management
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO and Memory Management


  • Subject: Re: WO and Memory Management
  • From: Owen McKerrow <email@hidden>
  • Date: Fri, 14 Jul 2006 12:33:15 +1000

Thanks for the response Chuck. See comments below....

On 14/07/2006, at 11:53 AM, Chuck Hill wrote:


On Jul 13, 2006, at 6:15 PM, Owen McKerrow wrote:

Hi All,

We are setting up an application of ours on a clients server, they did some stress testing to see if they needed a bigger box and discovered something strange.
Their comments ....


The webobjects versions have been stress tested further, we are getting ok
results but far worse then I was hoping. RIS Public faired worse the RIS
with it starting to get error with only 5 simultaneous users making simple
request 5 seconds apart (running with 2 instances each with -mx512M.

That is odd. Are you dispatching requests concurrently?

No, getting them to retest with it on.



A major point of interest is that garbage collection does not appear to be
active for these instances.

Check for I/O and DB usage. How long does the average request take to process?

From the stats page : Transactions 691 Active Session 0 Average transactions 5.031 Averegae idle 131.627



We ran the tests yesterday and the started to
consume over 500M per instance (2 instance running for RIS and RISPublic).
This morning after no activity all night the process are still using the
full memory set. To me this is a bit of a concern, can you guys check your
side to see if it the same there, or if there is some configuration options
that can be put in place to improve this?

The strange thing here is that the instances don't seem to be releasing memory. Is this normal ? Is there a setting I need to tweak somewhere in JavaMonitor ?

This is normal for the JVM on OS X. Once the JVM has allocated memory, it does not return it to the OS until it terminates. You can have the instances restart more often to return this memory to the OS. 500M seems like a lot, but that depends on what the app is doing.

Sorry forgot to mention its on a Solaris Machine running Vs 9. WO 5.2.4 ( witha 5.3 build if it makes any difference ).




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: WO and Memory Management
      • From: Chuck Hill <email@hidden>
References: 
 >WO and Memory Management (From: Owen McKerrow <email@hidden>)
 >Re: WO and Memory Management (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Voting Time.. Food/Policy for WoDev event, August 7th 7-10pm
  • Next by Date: Re: WO and Memory Management
  • Previous by thread: Re: WO and Memory Management
  • Next by thread: Re: WO and Memory Management
  • Index(es):
    • Date
    • Thread