[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dropping and memory usage.
From: |
David Sumpter |
Subject: |
Re: Dropping and memory usage. |
Date: |
Fri, 5 Jun 1998 14:34:27 +0100 |
> From address@hidden Thu Jun 4 18:59:49 1998
>
> Perhaps if you send -xfprint to the schedule and -xprint to the Swarm's zone,
> you'll be able to see what unexpected actions and/or objects are accumulating.
>
Hi theres two things which are accumulating,
number of internal objects: 16027 total size: 447884
gets bigger each step and,
at time: 0 action is: [0x2ade38: ConcurrentGroup_c (concurrent group)]
at time: 1 action is: [0x2d0c28: ConcurrentGroup_c (concurrent group)]
at time: 2 action is: [0x2c8410: ConcurrentGroup_c (concurrent group)]
......
at time: 67 action is: [0x3729a0: ConcurrentGroup_c (concurrent group)]
at time: 68 action is: [0x375210: ConcurrentGroup_c (concurrent group)]
at time: 69 action is: [0x377b98: ConcurrentGroup_c (concurrent group)]
adds a new action on each step. I think its the objects which are causing the
program to grow most.
I don't know what to look for when getting rid of internal objects?
Regards,
David
==================================
Swarm-Support is for discussion of the technical details of the day
to day usage of Swarm. For list administration needs (esp.
[un]subscribing), please send a message to <address@hidden>
with "help" in the body of the message.
==================================