Alex
normally I integrated the fixes of juan long time ago. Now could you have a
look at CUIS to see if you get the same effect.
Stef
On Dec 24, 2011, at 3:29 PM, Alexandre Bergel wrote:
>> This means that some other process (probably the finalization process, since
>> #factorial creates a lot of garbage) was running and/or gc happened during
>> the "missing" 34.2%. The gc times are listed below.
>
> I also thought about that. But I doubt this is the only reason. I tried:
>
> MessageTally spyOn: [ 100 timesRepeat: [XMLDOMParser parse: (FileStream
> fileNamed: 'path to an xml file') contents ]].
>
> and I obtain
> -=-=-=-=-=-=-=-=-=-=-=-=
> - 168 tallies, 168 msec.
>
> **Tree**
> --------------------------------
> Process: (40s) 754188288: nil
> --------------------------------
> 18.5% {31ms} XMLDOMParser>>parseDocument
> 18.5% {31ms} XMLDOMParser(SAXHandler)>>parseDocument
> 18.5% {31ms} XMLParser>>parseDocument
> 18.5% {31ms} XMLParser>>parseToken
> 18.5% {31ms} XMLTokenizer>>nextToken
> 16.1% {27ms} XMLTokenizer>>nextMarkupToken
> -=-=-=-=-=-=-=-=-=-=-=-=
>
> The memory stat are
> -=-=-=-=-=-=-=-=-=-=-=-=
>
> **Memory**
> old +120,524 bytes
> young -442,960 bytes
> used -322,436 bytes
> free +322,436 bytes
>
> **GCs**
> full 0 totalling 0ms (0.0% uptime)
> incr 12 totalling 5ms (3.0% uptime), avg 0.0ms
> tenures 2 (avg 6 GCs/tenure)
> root table 0 overflows
> -=-=-=-=-=-=-=-=-=-=-=-=
>
>
> The factorial example consumes more memory, and it is reported to consume 72%
>
> Something is weird. I will look into it.
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
