[Pharo-project] Any theme or settings that will speed up a Pharo 1.3 image?
Hi: When trying to debug a Pharo image with a VM that is heavily instrumented with assertions and runs without any compiler optimizations turned on, it is crawlingly slow. (The good old MVC based image is blazingly fast in comparison) Are there any tricks to reduce/disable all the possibly fancy things like transparency, code completion, syntax highlighting easily? I already disable the code completion, and syntax highlighting. I also switched off things like animations, rounded corners, and switched to the Standard Squeak theme. Still, non of these cosmetic changes gave me the noticeable performance gain I had hoped for. Is there anything else I could try to reduce the amount of work the image is doing? It blinks the cursor in a text field in the speed I would expect. But as soon as I start typing, or try to interact with a window, it feels like I can go for a walk before the image is done. Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
hi stefan, maybe you can try yo profile all threads and see where it actually spends all the time? WorldMenu / System / Start profiling all Processes best cami On 2012-03-18, at 12:57, Stefan Marr wrote:
Hi:
When trying to debug a Pharo image with a VM that is heavily instrumented with assertions and runs without any compiler optimizations turned on, it is crawlingly slow. (The good old MVC based image is blazingly fast in comparison)
Are there any tricks to reduce/disable all the possibly fancy things like transparency, code completion, syntax highlighting easily?
I already disable the code completion, and syntax highlighting. I also switched off things like animations, rounded corners, and switched to the Standard Squeak theme.
Still, non of these cosmetic changes gave me the noticeable performance gain I had hoped for.
Is there anything else I could try to reduce the amount of work the image is doing? It blinks the cursor in a text field in the speed I would expect. But as soon as I start typing, or try to interact with a window, it feels like I can go for a walk before the image is done.
Thanks Stefan
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
On Sun, Mar 18, 2012 at 4:57 AM, Stefan Marr <smalltalk@stefan-marr.de>wrote:
Hi:
When trying to debug a Pharo image with a VM that is heavily instrumented with assertions and runs without any compiler optimizations turned on, it is crawlingly slow. (The good old MVC based image is blazingly fast in comparison)
Are there any tricks to reduce/disable all the possibly fancy things like transparency, code completion, syntax highlighting easily?
I already disable the code completion, and syntax highlighting. I also switched off things like animations, rounded corners, and switched to the Standard Squeak theme.
Still, non of these cosmetic changes gave me the noticeable performance gain I had hoped for.
Is there anything else I could try to reduce the amount of work the image is doing? It blinks the cursor in a text field in the speed I would expect. But as soon as I start typing, or try to interact with a window, it feels like I can go for a walk before the image is done.
I noticed some absurd preference checking in standard images a while back, but turning this off made no noticeable different in optimized Cog. Look for uses of Preferences subPixelRenderFonts, e.g. installStrikeFont: foregroundColor:backgroundColor:. There's a non-local return in the default path on preference access. So not having subPixelRenderFonts a defined preference method creates lots on noise when doing VM debugging.
Thanks Stefan
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
-- best, Eliot
Hi: On 19 Mar 2012, at 18:08, Eliot Miranda wrote:
I noticed some absurd preference checking in standard images a while back, but turning this off made no noticeable different in optimized Cog. Look for uses of Preferences subPixelRenderFonts, e.g. installStrikeFont:foregroundColor:backgroundColor:. There's a non-local return in the default path on preference access. So not having subPixelRenderFonts a defined preference method creates lots on noise when doing VM debugging.
In the Pharo 1.3 image, that does not look like a problem. #subPixelRenderFonts is only defined in StrikeFont class and does a quick ^ true. One thing I noticed is that the amount of open windows has a hugh impact on the speed. Camillo, profiling only told me that the RoarVM apparently does not support it ;) The same experiment on Cog didn't show anything interesting either. At least nothing obvious. You used your own images for Pinocchio, or was Pinocchio just fast enough for the standard images? Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
participants (3)
-
Camillo Bruni -
Eliot Miranda -
Stefan Marr