[Pharo-dev] Large images reasons [WAS] Re: [Pharo-users] Pharo 2.0 with Seaside + DBXTalk + GlorpDBX + Magritte 3 + TWBS is getting slower and slower

Marcus Denker marcus.denker at inria.fr
Thu Aug 1 07:40:25 EDT 2013


Yes, I think the announcers of morph might be the cause of the problem...


On Thu, Aug 1, 2013 at 1:09 PM, phil at highoctane.be <phil at highoctane.be>wrote:

> I did a little run on those MorphExtensions and got the output file in
> annex.
>
> Cursor wait showWhile: [
> (FileSystem disk workingDirectory / 'MorphExtensions.txt') asFileReference
> writeStreamDo: [  :s |
>  MorphExtension allInstancesDo: [ :each |
> each printOn: s.
>       s lf
>  ]
> ]
> ].
>
> Looks like there are a lot of Announcers.
>
> Phil
>
>
> On Thu, Aug 1, 2013 at 9:35 AM, Marcus Denker <marcus.denker at inria.fr>wrote:
>
>>
>> On Aug 1, 2013, at 1:31 AM, phil at highoctane.be wrote:
>>
>> Doing the flushCaches...
>>
>> Image size before cleaning a MCSmalltalkhubRepository(
>> http://smalltalkhub.com/mc/estebanlm/EclipsePack/main/) : 324017564
>> Image size after cleaning a MCSmalltalkhubRepository(
>> http://smalltalkhub.com/mc/estebanlm/EclipsePack/main/) : 324137232
>> Image size before cleaning a MCSmalltalkhubRepository(
>> http://smalltalkhub.com/mc/philippeback/DripfeedIt/main/) : 324137232
>> Image size after cleaning a MCSmalltalkhubRepository(
>> http://smalltalkhub.com/mc/philippeback/DripfeedIt/main/) : 324195720
>> Image size before cleaning a MCSmalltalkhubRepository(
>> http://smalltalkhub.com/mc/philippeback/HOWebStack/main/) : 324195720
>> Image size after cleaning a MCSmalltalkhubRepository(
>> http://smalltalkhub.com/mc/philippeback/HOWebStack/main/) : 324255300
>> Image size before cleaning a MCSmalltalkhubRepository(
>> http://smalltalkhub.com/mc/philippeback/HOExperiments/main/) : 324255300
>> Image size after cleaning a MCSmalltalkhubRepository(
>> http://smalltalkhub.com/mc/philippeback/HOExperiments/main/) : 324314868
>>
>> Definitely not going down...
>>
>>
>> No, we already saw that in your case the reason are many,many instances
>> of MorphExtension without the Morphs hanging around.
>> (which should not happen as MorphExtensions are only referenced by the
>> Morph they extend).
>>
>> Your case is not a case of caches, there is a real problem somewhere.
>>
>> Marcus
>>
>>
>


-- 
--
Marcus Denker  --  denker at acm.org
http://www.marcusdenker.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20130801/6dd182ae/attachment-0002.html>


More information about the Pharo-dev mailing list