[Fix] Issue890 Mantis6535 SortedCollection loose sortBlock

>> OB is another story. For me, its at the border of being usable  
>> because
>> of its slowness.
>
> Just for the record: OB included with the Seaside One-Click image is
> only marginally slower than the standard system browser.
>
>   Opening and closing OB system browser on the class WACounter:  
> 636.15 ms
>   Opening and closing SystemBrowser on the class WACounter: 555.00 ms
>
> Lukas
>
> -=--=--=--=--=--=--=--=--=--=--=--=--=--=-
>
> " Omni Browser "
> [ browsers := (1 to: 20)
> collect: [ :each | OBSystemBrowser onClass: WACounter ].
> browsers do: [ :each |
> each open.
> World doOneCycle ].
> browsers do: [ :each |
> each close.
> World doOneCycle ] ]
> timeToRun / 20.0
>
> " System Browser "
> [ browsers := (1 to: 20)
> collect: [ :each | Browser new setClass: WACounter selector: nil ].
> browsers do: [ :each |
> Browser openBrowserView: (each openEditString: nil) label: 'System  
> Browser'.
> World doOneCycle ].
> browsers do: [ :each |
> each changed: #close.
> World doOneCycle ] ]
> timeToRun / 20.0
>
> -=--=--=--=--=--=--=--=--=--=--=--=--=--=-
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>> OB is another story. For me, its at the border of being usable  
>> because
>> of its slowness.
>
> Just for the record: OB included with the Seaside One-Click image is
> only marginally slower than the standard system browser.
>
>   Opening and closing OB system browser on the class WACounter:  
> 636.15 ms
>   Opening and closing SystemBrowser on the class WACounter: 555.00 ms
>
> Lukas
>
> -=--=--=--=--=--=--=--=--=--=--=--=--=--=-
>
> " Omni Browser "
> [ browsers := (1 to: 20)
> collect: [ :each | OBSystemBrowser onClass: WACounter ].
> browsers do: [ :each |
> each open.
> World doOneCycle ].
> browsers do: [ :each |
> each close.
> World doOneCycle ] ]
> timeToRun / 20.0
>
> " System Browser "
> [ browsers := (1 to: 20)
> collect: [ :each | Browser new setClass: WACounter selector: nil ].
> browsers do: [ :each |
> Browser openBrowserView: (each openEditString: nil) label: 'System  
> Browser'.
> World doOneCycle ].
> browsers do: [ :each |
> each changed: #close.
> World doOneCycle ] ]
> timeToRun / 20.0
>
> -=--=--=--=--=--=--=--=--=--=--=--=--=--=-
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Thanks, I like benchmarks! I've run this in the recent Pharo-core and
> Pharo images (on the class String):
>
> Pharo core 10432 SystemBrowser: 686.6ms
> Pharo0.1-10342dev09.06.3 SystemBrowser: 940.8ms
> Pharo0.1-10342dev09.06.3 OBSystemBrowser: 1087.1ms
>
> Similar to Lukas' results is that the OBSystemBrowser is not that much
> slower than the normal SystemBrowser (slowdown of 15%). However, there
> is a larger difference between the SystemBrowser in Pharo and in  
> Pharo-
> core (37%). Hence other features seem to contribute to the slowdown:
> freetype fonts, code highlighting, ...?
>
> Adrian
>
> On Jun 17, 2009, at 11:18 , Lukas Renggli wrote:
>
>>> OB is another story. For me, its at the border of being usable
>>> because
>>> of its slowness.
>>
>> Just for the record: OB included with the Seaside One-Click image is
>> only marginally slower than the standard system browser.
>>
>>  Opening and closing OB system browser on the class WACounter:
>> 636.15 ms
>>  Opening and closing SystemBrowser on the class WACounter: 555.00 ms
>>
>> Lukas
>>
>> -=--=--=--=--=--=--=--=--=--=--=--=--=--=-
>>
>> " Omni Browser "
>> [ browsers := (1 to: 20)
>> collect: [ :each | OBSystemBrowser onClass: WACounter ].
>> browsers do: [ :each |
>> each open.
>> World doOneCycle ].
>> browsers do: [ :each |
>> each close.
>> World doOneCycle ] ]
>> timeToRun / 20.0
>>
>> " System Browser "
>> [ browsers := (1 to: 20)
>> collect: [ :each | Browser new setClass: WACounter selector: nil ].
>> browsers do: [ :each |
>> Browser openBrowserView: (each openEditString: nil) label: 'System
>> Browser'.
>> World doOneCycle ].
>> browsers do: [ :each |
>> each changed: #close.
>> World doOneCycle ] ]
>> timeToRun / 20.0
>>
>> -=--=--=--=--=--=--=--=--=--=--=--=--=--=-
>>
>> --
>> Lukas Renggli
>> http://www.lukas-renggli.ch
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Hi Nicolas,
>
> On Jun 16, 2009, at 22:10 , Nicolas Cellier wrote:
>
> [...]
>
>> <rant>
>> Monticello is quite a drag, and pharo feels globally unresponsive
>> (even the core image).
>
> Yep, responsiveness can be improved. The core feels quite fast for me
> (on a MacBook Pro), but still, for example opening a browser is not
> instantaneous. Also, if you type really fast, the characters start
> appearing late (I think Bill complained about that recently).
>
> OB is another story. For me, its at the border of being usable because
> of its slowness.

> On Wed, Jun 17, 2009 at 2:32 PM, Marcus Denker<[hidden email]> wrote:
>> I wonder if OB would not be much faster if the auto-category feature
>> would
>> be turned off?
>
> are you talking about the dynamic protocols (long methods,
> override...)? They are much faster than before. You can disable them
> to see if they are a source of slowdowns by going to the preference
> browser, 'dynamic protocols' category.
>