April 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Slower

by Hilaire

It is already animated :) https://twitter.com/GNUDrGeo/status/981583820037160961 But canvas get slow when I push to 500 montecarlo iterations, for example. Le 04/04/2018 Ã 19:03, Stephane Ducasse a Ã©critÂ : > Hilaire > > do you want to see an animation? > > Stef -- Dr. Geo http://drgeo.eu

April 4, 2018

Re: [Pharo-users] Slower

by Stephane Ducasse

Hilaire do you want to see an animation? Stef On Wed, Apr 4, 2018 at 3:49 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > I discover this Dr. Geo Smalltalk sketch to animate is about 60% slowler on > P7 compare to P3: > > | fig point comment x y random inArc tries| > "Monte-Carlo PI approximation" > fig := DrGeoCanvas new fullscreen scale: 400. > fig arcCenter: 0@0 from: 1@0 to: 0@1. > fig polygon: { 0@0. 0@1. 1@1. 1@0 }. > comment := fig texte: '' a: 0@ -0.1. > random := Random seed: Time millisecondClockValue. > tries := 500. > inArc := 0. > [1 a: tries faire: [: try | > x := random next. > y := random next. > point := (fig point: x@y) small. > (x squared + y squared) > 1 > ifTrue: [point color: Color blue ] > ifFalse: [inArc := inArc + 1 ]. > comment text: 'Tries: ', try asString, ' > approx: ', (inArc * 4 / try) asFloat asString. > World doOneCycle. > ] ] timeProfile > > The log are enclosed to compare. The mains differences seems to be during > the world update. Years ago when porting to P3 I also see an important time > performance degradation[1] and it remained unresolved. > > > [1] http://forum.world.st/Slowness-question-tt4761717.html > > > > > -- > Dr. Geo > http://drgeo.eu >

April 4, 2018

Re: [Pharo-users] Slower

by Stephane Ducasse

Clement if it would be nice to have the fastCorner and friends added to rectangle. On Wed, Apr 4, 2018 at 5:33 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hi Hilaire, > > Do you have to use the world or Morphic at all ? > > I wrote 2 different real-time 2D games at 50fps in Pharo [1,2]. I tried > using Morphic but that was crazy slow I could not even get 20fps. Instead I > use direct bindings to Cairo surface and SDL2 window and I don't open the > world morph at all to avoid the delays due to its cycles which are also > crazy (I open Pharo in headless, then the Pharo code opens a SDL2 window and > draws on it using Cairo). Then I was just careful on the number of > allocations, especially closures, in between frame rendering and also on > algorithms (I had 60% of time spent creating rectangle in corner: since it > performs a lot of min max computation, rewriting that to fastCorner method > without min max greatly improved the performance in my case). I still have > frame drops from time to time but that's hardly noticeable. > > If you're scared of using Cairo / SDL2 because you deploy on specific > platforms like mobiles, you can still use BitBlt. The point being not to run > WorldMorph cycles at all but instead manage yourself what is drawn. If > possible don't use Morph at all too, it has many features that likely you > don't use, slowing down your system and wasting battery on mobiles for > nothing. > > [1] https://github.com/clementbera/wizard-battle-arena > [2] https://github.com/clementbera/SpiderInvasion > > > On Wed, Apr 4, 2018, 15:49 Hilaire <hilaire(a)drgeo.eu> wrote: >> >> Hi, >> >> I discover this Dr. Geo Smalltalk sketch to animate is about 60% slowler >> on P7 compare to P3: >> >> | fig point comment x y random inArc tries| >> "Monte-Carlo PI approximation" >> fig := DrGeoCanvas new fullscreen scale: 400. >> fig arcCenter: 0@0 from: 1@0 to: 0@1. >> fig polygon: { 0@0. 0@1. 1@1. 1@0 }. >> comment := fig texte: '' a: 0@ -0.1. >> random := Random seed: Time millisecondClockValue. >> tries := 500. >> inArc := 0. >> [1 a: tries faire: [: try | >> x := random next. >> y := random next. >> point := (fig point: x@y) small. >> (x squared + y squared) > 1 >> ifTrue: [point color: Color blue ] >> ifFalse: [inArc := inArc + 1 ]. >> comment text: 'Tries: ', try asString, ' >> approx: ', (inArc * 4 / try) asFloat asString. >> World doOneCycle. >> ] ] timeProfile >> >> The log are enclosed to compare. The mains differences seems to be >> during the world update. Years ago when porting to P3 I also see an >> important time performance degradation[1] and it remained unresolved. >> >> >> [1] http://forum.world.st/Slowness-question-tt4761717.html >> >> >> >> >> -- >> Dr. Geo >> http://drgeo.eu >> >

April 4, 2018

Re: [Pharo-users] Slower

by Hilaire

Hi Clement, I know about your SDL games demo. But DrGeo is really Morphic based, so yes it is mandatory. I suspect there is may be something going on between Cairo/Athens/Morph. For regular mouse use of DrGeo it is just fine. It is when pusing to the limite with Smalltalk sketch and animating the resulting sktech. Le 04/04/2018 Ã 17:33, ClÃ©ment Bera a Ã©critÂ : > Hi Hilaire, > > Do you have to use the world or Morphic at all ? > -- Dr. Geo http://drgeo.eu

April 4, 2018

Re: [Pharo-users] Slower

by ClÃ©ment Bera

Hi Hilaire, Do you have to use the world or Morphic at all ? I wrote 2 different real-time 2D games at 50fps in Pharo [1,2]. I tried using Morphic but that was crazy slow I could not even get 20fps. Instead I use direct bindings to Cairo surface and SDL2 window and I don't open the world morph at all to avoid the delays due to its cycles which are also crazy (I open Pharo in headless, then the Pharo code opens a SDL2 window and draws on it using Cairo). Then I was just careful on the number of allocations, especially closures, in between frame rendering and also on algorithms (I had 60% of time spent creating rectangle in corner: since it performs a lot of min max computation, rewriting that to fastCorner method without min max greatly improved the performance in my case). I still have frame drops from time to time but that's hardly noticeable. If you're scared of using Cairo / SDL2 because you deploy on specific platforms like mobiles, you can still use BitBlt. The point being not to run WorldMorph cycles at all but instead manage yourself what is drawn. If possible don't use Morph at all too, it has many features that likely you don't use, slowing down your system and wasting battery on mobiles for nothing. [1] https://github.com/clementbera/wizard-battle-arena [2] https://github.com/clementbera/SpiderInvasion On Wed, Apr 4, 2018, 15:49 Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > I discover this Dr. Geo Smalltalk sketch to animate is about 60% slowler > on P7 compare to P3: > > | fig point comment x y random inArc tries| > "Monte-Carlo PI approximation" > fig := DrGeoCanvas new fullscreen scale: 400. > fig arcCenter: 0@0 from: 1@0 to: 0@1. > fig polygon: { 0@0. 0@1. 1@1. 1@0 }. > comment := fig texte: '' a: 0@ -0.1. > random := Random seed: Time millisecondClockValue. > tries := 500. > inArc := 0. > [1 a: tries faire: [: try | > x := random next. > y := random next. > point := (fig point: x@y) small. > (x squared + y squared) > 1 > ifTrue: [point color: Color blue ] > ifFalse: [inArc := inArc + 1 ]. > comment text: 'Tries: ', try asString, ' > approx: ', (inArc * 4 / try) asFloat asString. > World doOneCycle. > ] ] timeProfile > > The log are enclosed to compare. The mains differences seems to be > during the world update. Years ago when porting to P3 I also see an > important time performance degradation[1] and it remained unresolved. > > > [1] http://forum.world.st/Slowness-question-tt4761717.html > > > > > -- > Dr. Geo > http://drgeo.eu > >

April 4, 2018

Slower

by Hilaire

Hi, I discover this Dr. Geo Smalltalk sketch to animate is about 60% slowler on P7 compare to P3: | fig point comment x y random inArc tries| "Monte-Carlo PI approximation" fig := DrGeoCanvas new fullscreen scale: 400. fig arcCenter: 0@0 from:Â 1@0 to: 0@1. fig polygon: { 0@0. 0@1. 1@1. 1@0 }. comment := fig texte: '' a: 0@ -0.1. random := Random seed: Time millisecondClockValue. tries := 500. inArc := 0. [1 a: tries faire: [: try | Â Â Â x := random next. Â Â Â y := random next. Â Â Â point := (fig point: x@y) small. Â Â Â (x squared + y squared) > 1 Â Â Â Â Â Â ifTrue: [point color: Color blueÂ ] Â Â Â Â Â Â ifFalse: [inArc := inArc + 1 ]. comment text: 'Tries: ', try asString, ' approx: ', (inArc * 4 / try) asFloat asString. World doOneCycle. ] ] timeProfile The log are enclosed to compare. The mains differences seems to be during the world update. Years ago when porting to P3 I also see an important time performance degradation[1] and it remained unresolved. [1] http://forum.world.st/Slowness-question-tt4761717.html -- Dr. Geo http://drgeo.eu

April 4, 2018

Re: [Pharo-users] About async web stuff

by Guillermo Polito

Well, nothing we don't already have with Zinc, green threads, taskit and generators (+ syntax sugar). The nicest thing is however: http://www.tornadoweb.org/en/stable/ioloop.html#i-o-events They have a nice library to do async IO. We have also one but we do not exploit it enough I think. This is nice because it would simplify the implementation of all external code calling Pharo. In that front we currently have some spaghetti: - the input event fetcher implements an async queue of UI events whose consumer is a process in the image and the producer is the VM. - sockets and the async io plugin have a different approach, also written in the VM. - callbacks should also use a similar approach to notify when they are being called from C. On Wed, Apr 4, 2018 at 12:40 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > Am 04.04.2018 um 12:12 schrieb Stephane Ducasse <stepharo.self(a)gmail.com > >: > > > > Iâm not good enough to understand it simply :) > > But you are :) > > > > http://www.tornadoweb.org/en/stable/guide/intro.html > > > It is about âhow to program in python as you would in javascriptâ. > > Norbert > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

April 4, 2018

Re: [Pharo-users] To be there or not to be there

by Hilaire

Le 04/04/2018 Ã 11:19, Denis Kudriashov a Ã©critÂ : > How you performed renaming? From package pane menu/shortcut? From pane menu > > When you rename DrGeoII-Polymorph to DrGeoII-UI the last was already > exists? Not it did not exist. -- Dr. Geo http://drgeo.eu

April 4, 2018

Re: [Pharo-users] About async web stuff

by Norbert Hartl

> Am 04.04.2018 um 12:12 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Iâm not good enough to understand it simply :) > But you are :) > > http://www.tornadoweb.org/en/stable/guide/intro.html > It is about âhow to program in python as you would in javascriptâ. Norbert

April 4, 2018

Re: [Pharo-users] Black screen on Mac OSX

by Stephane Ducasse

I have the impression that there is something with source and cr. I'm busy with a project proposal. Let me know for P7 because this is easier to check and help. On Tue, Apr 3, 2018 at 11:31 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > No I am not defining such extra method. I more or less packaged blindly a > modified universal VMs for P4. I was able to test it on linux and windows > (throught wine), but not on Mac osx. > > I am doing right now the same for P7 based image, but not there yet. > > > Le 03/04/2018 Ã 22:39, Stephane Ducasse a Ã©crit : >> >> Hilaire >> >> I looked at the other bug. >> And I would like to know if you are defining extra >> methods on SQSurfaceDispatch class. >> I do not get why I got an error (may be this is related to the source >> management. >> >> Stef > > > -- > Dr. Geo > http://drgeo.eu > > >

April 4, 2018