Unusually long tactile delays when using the debugger

[Shaping]

Pharo version: 10 64-bit (stable) OS: Windows 10 Pro

It's a great looking debugger. The information is rich. The rendering, though is slow.

If I select a line in the call stack, the fill-delay is about 200 ms. Terrible. I'm falling asleep already.

If I select a variable in the lower-left pane, the fill-delay is about 150 ms, also bad. I'm still losing my focus.

These delays are a serious ergonomic problem--not good if you wish to maintain a healthy nervous system and fluid thought stream.

I'll assume there are deeper rendering problems causing these delays. Can some one give me the scoop? Where are the bottlenecks and weaknesses in the rendering and update path? I will work on the solution if someone can sketch the overall problem and mention the specific class names involved.

This is hard to tolerate--but it looks great.

The delays should be at most 50 ms, maybe 70 ms if you want to stretch. Better would be 10 to 20 ms, but I'm not expecting that performance level until the VM technology is substantially better. If the VM is the problem, please, if you can, describe the problem in as much detail as possible, and point me to the most recent, most relevant docs that will help me understand the performance issues, so that I can work on the problem. ....

BTW, the above debugger opened when I executed the following script:

Download pharo VM and image Open your Pharo image Open Iceberg Click the Add repository button Select Clone from github.com and enter ba-st as owner name and Willow-SemanticUI as project name Click Ok

The above script is the one given here https://github.com/ba-st/Willow-SemanticUI/blob/release-candidate/docs/how-to/how-to-load-in-pharo.md for loading Willow-Semantic-UI. I don't understand the Git error. That may be a separate bug, but I suspect I may not have Git fully configured/prepared, though I would think that the instructions would include those steps too.

Examination of the specified ba-st folder shows that the repo was in fact copied to the local hard drive. I don't know why the clone operation didn't finish successfully. Please suggest a solution. I would like to test Willow,

If I should generate a separate issue for the Willow bug, please advise.