Oz Panel and heap size

[Torsten Anders]

No-one complained, so I committed the changes of the SGML doc file to  
SVN. Unfortunately, I can not test and build the doc, as I am on  
MacOS...

Best
Torsten

On Sep 24, 2007, at 6:55 PM, Torsten Anders wrote:
> Dear Kevin, dear Boris,
>
> thanks for your replies. Below is a draft of what could be added to  
> the Panel doc. I suggest adding it to the first chapter  
> "Usage" (http://www.mozart-oz.org/documentation/panel/ 
> node1.html#chapter.usage). Any comments?
>
> Best
> Torsten
>
>
> Add to Panel doc:
>
> Please note that the Panel application itself contributes to thread  
> and memory usage. For example, whenever the panel display updates  
> the heap usage (by default, every second when the mouse pointer is  
> over the panel application) the current heap size increases by a  
> few KB. Moreover, in the default setting two new threads are  
> created whenever the mouse is moved anew over the panel, or when  
> tabs are switched (the number of runnable threads remains 1, though).
>
>
>
> On Sep 24, 2007, at 5:26 PM, Boriss Mejias wrote:
>> Hi Torsten,
>>
>> The panel indeed consumes memory and it is a good idea to mention  
>> it in
>> the documentation. We should do the same with threads, because I have
>> notices that every time you place the mouse over the panel, the  
>> system
>> creates two threads.
>>
>> By the way, a useful tip for using the panel is to go to Options- 
>> >Update
>> and then unclick the option "Require Mouse over Panel". Setting the
>> Update Time to 500ms is also something I usually do.
>>
>> cheers
>> Boriss
>>
>> Torsten Anders wrote:
>>> Dear all,
>>>
>>> I am just studying the memory consumption of some program with  
>>> the handy
>>> system panel.
>>>
>>> I noticed that whenever the panel is constantly updating (i.e.  
>>> when the
>>> mouse pointer is over the Panel's window), the current heap size
>>> increases by about 3 K per second -- even if no other Oz code at  
>>> all is
>>> loaded. As soon as the mouse is removed from the panel, the size  
>>> stays
>>> where it is. So, this memory consumption is probably caused by  
>>> the panel
>>> itself.
>>>
>>> I was far a while searching what my program does wrong before I  
>>> figured
>>> this out. It is of course totally fine that the panel reports its  
>>> own
>>> memory consumption, but some hint in the documentation might be  
>>> helpful.
>>>
>>> Can anyone confirm that this is indeed the case? Would it be OK  
>>> then, if
>>> I add a brief remark to the Panel doc (e.g., at
>>> http://www.mozart-oz.org/documentation/panel/ 
>>> node3.html#chapter.usage.memory)?
>>>
>>>
>>> Thanks!
>>>
>>> Best
>>> Torsten
>>>
>>> --
>>> Torsten Anders
>>> Interdisciplinary Centre for Computer Music Research
>>> University of Plymouth
>>> Office:   +44-1752-233667
>>> Private: +44-1752-663492
>>> http://strasheela.sourceforge.net
>>> http://www.torsten-anders.de
>>>
>>>
>>>
>>>
>>> ____________________________________________________________________ 
>>> _____________
>>>
>>> mozart-users mailing list
>>> mozart-users at mozart-oz.org
>>> http://www.mozart-oz.org/mailman/listinfo/mozart-users
>> _____________________________________________________________________ 
>> ____________
>> mozart-users mailing list                               mozart- 
>> users at mozart-oz.org
>> http://www.mozart-oz.org/mailman/listinfo/mozart-users
>
> --
> Torsten Anders
> Interdisciplinary Centre for Computer Music Research
> University of Plymouth
> Office:   +44-1752-233667
> Private: +44-1752-663492
> http://strasheela.sourceforge.net
> http://www.torsten-anders.de
>
>
>
>

--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
Office:   +44-1752-233667
Private: +44-1752-663492
http://strasheela.sourceforge.net
http://www.torsten-anders.de