tried with ChronosManager

[ ChronosManager open ] bench

5.6 per second

it opened around 30 instances and Morphic was crawling.

I profiled it and it reports that it spends a total 170ms which is consistent with bench. Around 50ms is spent only for loading the image of the secondary panel and from what I have seen loading the images and the font accounts around 90% of the time spent and then rest 10% is actually morphic + logic.

So from the looks of it , it looks like Morphic does not perform well with loaded images and external files.

On Sun, Nov 22, 2015 at 11:34 AM Thierry Goubier <thierry.goubier@gmail.com> wrote:

Hi all,

I would like to ask you, all of you, something significant when doing
GUI coding:

�� Pay attention to performance!

With the current state of our technology (Morphic, Bloc, whatever comes
next) your target should be one hundred milliseconds (100 ms), for
opening / redisplaying the widget.

Why?

- Because, in 10ms, Morphic can open and layout dozens of Morphs on a
low-end machine (1.4GHz Celeron).

- Because most of you work on 3GHz+ i7 Macbook Pro (so, at 10x the cpu
performance of that said Celeron).

- Because you are not to reproduce the past: that your current tools are
slow is no excuse.

- Because you now have well designed core widgets (FT) that behaves in
O(1) and opens fully loaded in 10's of milliseconds

So, profile and clean your code! Eliminate unneeded caches! Clean your
architectures! Avoid or mark slow code and bottlenecks!

And bring numbers when you want to criticize the performance of a
subsystem...

Thierry