initializeMemorySettingsProfileSeaSide
is in the pharo image also initializeMemorySettingsProfileQF which I have no idea about... On 2010-01-07, at 2:12 AM, Adrian Lienhard wrote:
On Jan 6, 2010, at 22:09 , John M McIntosh wrote:
Oh sure Bill you're violating rule (a). In squeak a full finalization pass is require to finalize all objects. This runs in to the Pharo's desire to only do incremental GCs and avoid a full GC.
SystemDictionary>>setGCParameters
Smalltalk setGCBiasToGrowGCLimit: 16*1024*1024. Smalltalk setGCBiasToGrow: 1.
Which means that the image is happy to lurch around with a 16MB working space. Once that is exceeded then a full GC will occur. (yes yes, it's more complex that that, but it's just easier to say that's kinda what happens). The trade is deferring a full GC at the cost of deferring some finalized objects....
Frankly the default values for vmParameterAt: 5,6,24,25 I think are quite fictional based on desktop/laptop machines used in this decade, those values come from the era of 16Mhz 68030 macintosh SE/30 machines. However I do see that in initializeMemorySettingsProfileSeaSide someone picked more rational numbers but I think it's time that we clean those up this whole area.
Where can I find #initializeMemorySettingsProfileSeaSide? Could you propose new parameters for these settings? It's time to adjust them for the new decade ;)
Cheers, Adrian
[...]
-- =========================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================