April 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] RuntimeStorage

by Alexandre Bergel

Dear List, This morning, Jannik and I were surprised by the class RuntimeStorage. RuntimeStorage>>initialize: capacity byGroup := Dictionary new: 24. byName := IdentityDictionary new: 10000. elements := OrderedCollection new: capacity Why byName reference an identify dictionary? Why not a dictionary? Names are usually accessed through their name as a String apparently (e.g., importing Smalltalk packages keys entities with a String). Should entities be accessed through a symbol instead of a string? If entities are stored in an identity dictionary, then names must be accessed with a symbol. If entities are to be accessed with a string, then a dictionary should be used instead of an identitydictionary. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 21, 2009

[Pharo-project] OmniBrowser optimizations

by David RÃ¶thlisberger

Hi, Alex and me did some optimizations for the OmniBrowser framework. We focused on optimizing the updating of browser windows upon code changes (recompilation, recategorization, removing, doIts, etc.). Such browser updates are now an order of magnitude faster than before. For details, have a look at class OBBenchmarks in OB-Enhancements. To update you OmniBrowser installation, load the latest version of all installed OB-packages (typically OmniBrowser, OB-Standard, OB-Morphic, and OB-Enhancements) from http://source.wiresong.ca/ob. In Pharo, you can also execute 'ScriptLoader loadOBAlpha'. If you find any problems after this update, please let us know. Cheers, Alex and David

April 21, 2009

Re: [Pharo-project] Some bugs with the last version of pharo (10281) and pharo-dev (10284)

by Laval Jannik

Ok, I have found the problem: When I run the image for the first time, a folder "package-cache" is created. When the image is in a folder on my desktop ("/Users/jannik/Desktop/ Pharo"), it does not works. If I put this folder in "/Applications/Pharo", it works. Maybe, the bug come from the VM. Jannik On 21 avr. 09, at 09:04, Alexandre Bergel wrote: > It has to come from the packages loaded by Pharo-dev. I have no > problem with Pharo-Core > I experienced problem with eCompletion, but this is probably unrelated > to your situation. > > Alexandre > > > On 21 Apr 2009, at 08:13, Laval Jannik wrote: > >> Ok, >> >> I have always a bug with utf8: >> - it is impossible to open a Monticello browser because of an error >> "invalid utf8 input detected" >> - in the workspace of pharo-dev, there is the same error when I >> would like to run this line in a workspace: >> Installer monticello http: 'http://www.squeaksource.com'; project: >> 'Moose'; install: 'MooseLoader'. >> >> an idea ? >> >> Jannik >> >> On 20 avr. 09, at 18:22, Michael Rueger wrote: >> >>> On Mon, Apr 20, 2009 at 5:52 PM, Alexandre Bergel <alexandre(a)bergel.eu >>>> wrote: >>>> Strange. Cut&Paste works perfectly for me. I use >>>> Pharo0.1Core-10281cl >>>> and Squeak 4.0.1beta1U >>> >>> it's broken by the new event sensor stuff in 284 >>> >>> Michael >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 21, 2009

Re: [Pharo-project] Some bugs with the last version of pharo (10281) and pharo-dev (10284)

by Alexandre Bergel

It has to come from the packages loaded by Pharo-dev. I have no problem with Pharo-Core I experienced problem with eCompletion, but this is probably unrelated to your situation. Alexandre On 21 Apr 2009, at 08:13, Laval Jannik wrote: > Ok, > > I have always a bug with utf8: > - it is impossible to open a Monticello browser because of an error > "invalid utf8 input detected" > - in the workspace of pharo-dev, there is the same error when I > would like to run this line in a workspace: > Installer monticello http: 'http://www.squeaksource.com'; project: > 'Moose'; install: 'MooseLoader'. > > an idea ? > > Jannik > > On 20 avr. 09, at 18:22, Michael Rueger wrote: > >> On Mon, Apr 20, 2009 at 5:52 PM, Alexandre Bergel <alexandre(a)bergel.eu >> > wrote: >>> Strange. Cut&Paste works perfectly for me. I use >>> Pharo0.1Core-10281cl >>> and Squeak 4.0.1beta1U >> >> it's broken by the new event sensor stuff in 284 >> >> Michael >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 21, 2009

Re: [Pharo-project] Some bugs with the last version of pharo (10281) and pharo-dev (10284)

by Laval Jannik

Ok, I have always a bug with utf8: - it is impossible to open a Monticello browser because of an error "invalid utf8 input detected" - in the workspace of pharo-dev, there is the same error when I would like to run this line in a workspace: Installer monticello http: 'http://www.squeaksource.com'; project: 'Moose'; install: 'MooseLoader'. an idea ? Jannik On 20 avr. 09, at 18:22, Michael Rueger wrote: > On Mon, Apr 20, 2009 at 5:52 PM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: >> Strange. Cut&Paste works perfectly for me. I use Pharo0.1Core-10281cl >> and Squeak 4.0.1beta1U > > it's broken by the new event sensor stuff in 284 > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 21, 2009

Re: [Pharo-project] Issue 688 in pharo: Kernel concurrency fixes? 3.10

by Nicolas Cellier

Not me, I'm on linux and a simple printAllStacks() fulfiled my needs. Thanks 2009/4/21 John M McIntosh <johnmci(a)smalltalkconsulting.com>: > Does any one need such a VM? I would have to build a new one since the > old one is not closure based. > > On 20-Apr-09, at 1:24 PM, StÃ©phane Ducasse wrote: > >> I know that john has a vm with traces but I do not know how to do what >> you need. > > -- > = > = > = > ======================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Corporate Smalltalk Consulting Ltd. Â http://www.smalltalkconsulting.com > = > = > = > ======================================================================== > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 21, 2009

Re: [Pharo-project] Input sensor rewrite

by John M McIntosh

Aright I thought I'd better peer at this since it impacts those slow hand held devices (aka iphones). I took a pharo0.1-10284dev09.04.4 and did update I then count bytecodes executed and print that in ioRelinquishProcessorForMicroseconds So this Pharo image takes 51 million byte codes execute before we sleep. Likely this is the point were all the startup: stuff runs to completion. no windows open 51,249,233 bytes codes to idle now we print how many milliseconds we have calculated the image can sleep until the next wakeup due to a pending delay. for example 3 ms, and how many bytecodes were executed since the last time we slept, 2,409. Note the pattern of sleeping 10,2,4,9 ms and bytescodes executed of 442, 2409... 2009-04-20 20:56:39.634 Squeak VM Opt[2523:813] 3 2009-04-20 20:56:39.635 Squeak VM Opt[2523:813] 2409 2009-04-20 20:56:39.646 Squeak VM Opt[2523:813] 10 2009-04-20 20:56:39.647 Squeak VM Opt[2523:813] 426 2009-04-20 20:56:39.650 Squeak VM Opt[2523:813] 2 2009-04-20 20:56:39.651 Squeak VM Opt[2523:813] 422 2009-04-20 20:56:39.658 Squeak VM Opt[2523:813] 5 2009-04-20 20:56:39.659 Squeak VM Opt[2523:813] 2409 2009-04-20 20:56:39.670 Squeak VM Opt[2523:813] 9 2009-04-20 20:56:39.672 Squeak VM Opt[2523:813] 426 2009-04-20 20:56:39.684 Squeak VM Opt[2523:813] 10 2009-04-20 20:56:39.686 Squeak VM Opt[2523:813] 2630 2009-04-20 20:56:39.694 Squeak VM Opt[2523:813] 7 2009-04-20 20:56:39.695 Squeak VM Opt[2523:813] 422 2009-04-20 20:56:39.697 Squeak VM Opt[2523:813] 1 2009-04-20 20:56:39.698 Squeak VM Opt[2523:813] 2409 2009-04-20 20:56:39.711 Squeak VM Opt[2523:813] 10 2009-04-20 20:56:39.715 Squeak VM Opt[2523:813] 426 2009-04-20 20:56:39.729 Squeak VM Opt[2523:813] 10 2009-04-20 20:56:39.730 Squeak VM Opt[2523:813] 2630 But lets go back and look at mmm well an WIkiServer image based on Pharo from Jan or so. no windows open. Well first I do a lot less work (on purpose) at startup time 3,833,928 bytes code to idle, yes only 6% of the work... (ask me where March 09 went... ) but the other change is the morphic polling loop will send me off to slumber land for 20 ms given it's poll freq I think is targeting 50 fps. and the bytecodes executed each cycle is usually 2478 so it's very consistent. In production I turn server mode on and sleep for 500 ms since the UI events are driven by UIKit from screen taps, it's *all* about battery life... 2009-04-20 21:09:54.992 Squeak VM Opt[2624:813] 20 2009-04-20 21:09:54.994 Squeak VM Opt[2624:813] 2478 2009-04-20 21:09:55.020 Squeak VM Opt[2624:813] 20 2009-04-20 21:09:55.021 Squeak VM Opt[2624:813] 2478 2009-04-20 21:09:55.042 Squeak VM Opt[2624:813] 19 2009-04-20 21:09:55.043 Squeak VM Opt[2624:813] 2478 2009-04-20 21:09:55.064 Squeak VM Opt[2624:813] 19 2009-04-20 21:09:55.066 Squeak VM Opt[2624:813] 2478' 2009-04-20 21:09:55.085 Squeak VM Opt[2624:813] 15 2009-04-20 21:09:55.090 Squeak VM Opt[2624:813] 2474 2009-04-20 21:09:55.112 Squeak VM Opt[2624:813] 20 2009-04-20 21:09:55.112 Squeak VM Opt[2624:813] 2736 2009-04-20 21:09:55.137 Squeak VM Opt[2624:813] 19 2009-04-20 21:09:55.138 Squeak VM Opt[2624:813] 2478 2009-04-20 21:09:55.160 Squeak VM Opt[2624:813] 20 2009-04-20 21:09:55.160 Squeak VM Opt[2624:813] 2478 So I think here then in 40 ms we do about 5000 byte code but the new solution does about 8,722 or 75% more work with a more fractured sleep time. A random squeak 3.10 alpha 7082 image with a window or two open gives 7,390,552 byte codes executed to idle. A boring cycle, I note the 3,434 versus the iphone image 2,478, but this 3.10 image has 3 windows up so likely there is a bit more Morphic cycle time being chewed up. 2009-04-20 21:23:30.632 Squeak VM Opt[2683:813] 19 2009-04-20 21:23:30.632 Squeak VM Opt[2683:813] 3434 2009-04-20 21:23:30.653 Squeak VM Opt[2683:813] 20 2009-04-20 21:23:30.654 Squeak VM Opt[2683:813] 3434 2009-04-20 21:23:30.678 Squeak VM Opt[2683:813] 20 2009-04-20 21:23:30.679 Squeak VM Opt[2683:813] 3434 2009-04-20 21:23:30.705 Squeak VM Opt[2683:813] 20 2009-04-20 21:23:30.706 Squeak VM Opt[2683:813] 3434 2009-04-20 21:23:30.728 Squeak VM Opt[2683:813] 20 2009-04-20 21:23:30.728 Squeak VM Opt[2683:813] 3434 2009-04-20 21:23:30.753 Squeak VM Opt[2683:813] 18 2009-04-20 21:23:30.755 Squeak VM Opt[2683:813] 3434 2009-04-20 21:23:30.777 Squeak VM Opt[2683:813] 20 2009-04-20 21:23:30.777 Squeak VM Opt[2683:813] 3434 2009-04-20 21:23:30.798 Squeak VM Opt[2683:813] 19 2009-04-20 21:23:30.799 Squeak VM Opt[2683:813] 3434 2009-04-20 21:23:30.819 Squeak VM Opt[2683:813] 19 2009-04-20 21:23:30.820 Squeak VM Opt[2683:813] 3434 I'd like to see how the PURE EVENT driven event processing works, but not sure how to do that. Also I'm not sure what changes are in progress given the flurry of notes on the mailing list today and this evening. PS For poll driven VMs, couldn't you stick the event polling back in the morphic polling loop and just run one loop process? -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

April 21, 2009

Re: [Pharo-project] Issue 688 in pharo: Kernel concurrency fixes? 3.10

by John M McIntosh

Does any one need such a VM? I would have to build a new one since the old one is not closure based. On 20-Apr-09, at 1:24 PM, StÃ©phane Ducasse wrote: > I know that john has a vm with traces but I do not know how to do what > you need. -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

April 21, 2009

[Pharo-project] Pharo demo at BarCampHanoi'09

by Serge Stinckwich

Hi all, just a short breve : i use Pharo to make a demo during my Smalltalk talk at the last BarCamp Ha Noi'09 ;-) There is some pictures of my talk here : http://www.flickr.com/photos/crazyhands/3456228434/ http://www.flickr.com/photos/crazyhands/3455420077/ http://www.flickr.com/photos/gunner_ac50/3458847094/ I was pretty stable (more than last Squeak 3.10-dev where method finder doesn't not work ...). Thank you for the good work. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

April 21, 2009

Re: [Pharo-project] Delays Semaphores and Processes

by Igor Stasenko

Btw, guys since you working on this stuff, could you please check/try fixing this issue: http://bugs.squeak.org/view.php?id=6822 :) 2009/4/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > I'm :) > > Stef > > > On Apr 20, 2009, at 6:50 PM, Nicolas Cellier wrote: > >> That should! just try it... >> >> 2009/4/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> nicolas >> >> here is what I'm planning to do: >> >> Â Â Â Â 1- Â Delay startTimerEventLoop. >> Â Â Â Â 2- Merge your pakcage 300 >> Â Â Â Â 3- publish a new script and package >> Â Â Â Â Â Â Â Â with Â Delay startTimerEventLoop. >> >> Do you think that this will work? >> >> Stf >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

April 21, 2009