• 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: wotaskd/Monitor eating lot of RAM on Linux?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wotaskd/Monitor eating lot of RAM on Linux?


  • Subject: Re: wotaskd/Monitor eating lot of RAM on Linux?
  • From: Pascal Robert <email@hidden>
  • Date: Tue, 22 Jun 2010 12:51:51 -0400


Le 10-06-22 à 12:13, Aurélien Minet a écrit :

Hi Pascal

On 06/22/2010 03:49 PM, Pascal Robert wrote:
We are migrating our apps from OS X Server 10.4 to CentOS Linux
(x86_64), and everything is working fine. But I did notice something :
wotaskd and JavaMonitor are eating a lot more RAM. On the OS X box, they
take 41 MB each, on Linux they take up to 140 MB each :-/


The JVM on OS X is :

   Java HotSpot(TM) Server VM (build 1.5.0_13-121, mixed mode)

On Linux :

   Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)

So both are running the Server VM, the only different is Java 6 vs 5,
and 32 bits vs 64 bits. Still, I'm a bit amazed that it takes triple the
RAM. Both machines are running the same apps and the same number of
instances.


Anyone have seen this? It's not a problem, I just think it's a bit strange.


A few weeks ago I noticed that some of the wotaskd that were running were just in the top of memory consumers.
Actualy I have a wotaskd which has 42 instances running consuming ~285Mo (resident memory), it's a Wonder version
(06-01-2010 build for WO 5.3) running under Java 1.5 on an x86_32 Linux.
I noticed that Monitor consume memory too but less than wotaskd.
I had the idea of switching back to a vanilla version but profiling would be more helpful to understand why it's eating
so much memory.

Hum, I forgot to say that I also moved from the bundled version of wotaskd/Monitor to the Wonder versions. So since the Linux box is not in prod, I switched back to the 5.4.3 Apple version of the tools, and Monitor is eating 68 MB, wotaskd is eating 62 MB. If I switch back to the Wonder versions, wotaskd eats 107 MB, Monitor 73 MB.


So look like for whatever reason, Wonder's wotaskd eats almost double the RAM than the vanilla one :-/

----
Pascal Robert
email@hidden

AIM: MacTICanada
Twitter : MacTICanada
LinkedIn : http://www.linkedin.com/in/macti
WO Community profile : http://wocommunity.org/page/member?name=probert

_______________________________________________
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: wotaskd/Monitor eating lot of RAM on Linux?
      • From: Anjo Krank <email@hidden>
References: 
 >wotaskd/Monitor eating lot of RAM on Linux? (From: Pascal Robert <email@hidden>)
 >Re: wotaskd/Monitor eating lot of RAM on Linux? (From: Aurélien Minet <email@hidden>)

  • Prev by Date: Re: Weird error _NSAutoReleaseNoPool
  • Next by Date: Re: Weird error _NSAutoReleaseNoPool
  • Previous by thread: Re: wotaskd/Monitor eating lot of RAM on Linux?
  • Next by thread: Re: wotaskd/Monitor eating lot of RAM on Linux?
  • Index(es):
    • Date
    • Thread