So it should be a quick issue which would improve usability of the finder.
Apparently the bottleneck is at the creation of each group: we have to fill up the runtimestorage of the group and this includes an access to a dictionary. I am pretty sure the dictionary is useless in most case (because it's to retrieve elements by type, and groups usually contain one type of elements)
So, Jannik suggested to cache group creation when importing a model.
Or we can hope that the speed enhancements in pharo 1.1 make the thing better.
-- Simon
Hi,
I would go for the caching solution for the moment.
Cheers, Doru
On 26 Mar 2010, at 19:12, Simon Denier wrote:
So it should be a quick issue which would improve usability of the finder.
Apparently the bottleneck is at the creation of each group: we have to fill up the runtimestorage of the group and this includes an access to a dictionary. I am pretty sure the dictionary is useless in most case (because it's to retrieve elements by type, and groups usually contain one type of elements)
So, Jannik suggested to cache group creation when importing a model.
Or we can hope that the speed enhancements in pharo 1.1 make the thing better.
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."