[Pharo-dev] inspector performance improvement

Andrei Chis chisvasileandrei at gmail.com
Mon Feb 13 05:56:35 EST 2017


On Sun, Feb 12, 2017 at 5:07 PM, phil at highoctane.be <phil at highoctane.be> wrote:
> Any chance for this to run on a 5.0?

There are two main changes: moved inspector to fast table and some
fixes in the glamour renderer.
Moving the changes for the glamour renderer should be straightforward.
I can point you to the list of relevant commits if you want to make a
slice (We'll just need afterwards to also update
ConfigurationOfGlamourCore to still work for Pharo 5)

The FastTable changes could require more work but that should also be
doable. However, now we still have some issues to fix there so that's
not done for the moment.


Cheers,
Andrei


>
> Phil
>
> On Sun, Feb 12, 2017 at 3:13 PM, stepharong <stepharong at free.fr> wrote:
>>
>> Great job!!!!
>> It feels lot snappier :)
>> Now it is a real pleasure to navigate objects.
>> This is nice to see that you are paying attention because the engine is
>> getting faster and this is important
>> that the tools do not eat all the power by accident.
>> Tx a lot
>>
>>
>> On Sat, 11 Feb 2017 21:31:56 +0100, Tudor Girba <tudor at tudorgirba.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Andrei and Alex did a great job at improving the performance and
>>> scalability of the inspector.
>>>
>>> There are a couple of main improvements:
>>> - Added FastTable support for the Raw presentation for all objects. This
>>> implied completing the support for the tree presentation binding to fast
>>> table.
>>> - Moved the Items presentation for collections to FastTable.
>>> - Improved the rendering of Glamour to no longer rely on the default
>>> Morph>>#adoptPaneColor. It turns out that using adoptPaneColor triggers a
>>> relayout of the morph, even if it is not visible. We extended PanelMorph in
>>> the context of Glamour with a less needy logic.
>>>
>>> I will not tell you how fast it is. I would rather want you to play with
>>> it :).
>>>
>>> The change is already in the Moose image. It is not yet in Pharo, but it
>>> will be soon. In the meantime you can be load it in Pharo 6 like this:
>>>
>>>         Gofer new
>>>                 smalltalkhubUser: 'Moose' project: 'GToolkit';
>>>                 package: 'ConfigurationOfGToolkitCore';
>>>                 load.
>>>         (#ConfigurationOfGToolkitCore asClass project version: #stable)
>>> load
>>>
>>> To play with it, try this with both the current version and the new one
>>> and the Spec Inspector if you want (just make sure you save the image
>>> beforehand):
>>>
>>>         collection := (1 to: 100000000) asArray.
>>>         [collection inspect] timeToRun.
>>>
>>>         collection := (1 to: 100000000).
>>>         [collection inspect] timeToRun.
>>>
>>> (for these two ones notice that Items do not appear at all in the old
>>> implementation)
>>>
>>>         [World inspect] timeToRun.
>>>
>>>
>>> There are still a couple of issues open, such as the sorting of the
>>> columns. We would need your help with testing this, and report possible
>>> missing issues.
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>> www.feenk.com
>>>
>>> "Obvious things are difficult to teach."
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Using Opera's mail client: http://www.opera.com/mail/
>>
>



More information about the Pharo-dev mailing list