November 2015 - Pharo-dev - lists.pharo.org

[Pharo-project] Do we have the new primitive?? [WAS] Re: IdentitySet but using #hash rather than #identityHash ?
by Mariano Martinez Peck Dec. 16, 2015

Dec. 16, 2015

> All I can say is that I am impressed by the numbers it is really much >> faster. >> I still don't understand why I send this email with a subject say >> IdentitySet because what I really need is a fast/large IdentityDictionary >> :( Anyway, there's a place where we can use this LargeIdentitySet in Fuel >> I think). >> >> So Levente, you say this is not possible to adapt this for dictionary? >> can >> we contact Eliot to provide such a primitive? >> > > As promised, I uploaded my LargeIdentityDictionary implementation to > http://leves.web.elte.hu/**squeak/**LargeIdentityDictionary.st<http://leves.web.elte.hu/squeak/LargeIdentityDictionary.st>. > The numbers will be a bit worse compared to LargeIdentitySet, because of > the lack of the primitive, but it's still 2-3x faster than other solutions > (IdentityDictionary, PluggableIdentityDictionary, subclassing, etc). I'm > about to propose this primitive with other improvements on the vm-dev list. > > Hi Eliot/Levente. What is the status of this? Do we have already the new primitive? If true, how can we adapt LargeIdentitySet to use such new primitive? Thanks! > > Levente > > >> thanks >> >> On Fri, Dec 16, 2011 at 3:28 PM, Levente Uzonyi <leves(a)elte.hu> wrote: >> >> On Fri, 16 Dec 2011, Henrik Sperre Johansen wrote: >>> >>> On 16.12.2011 03:26, Levente Uzonyi wrote: >>> >>>> >>>> >>>>> How about my numbers? :) >>>>> >>>>> "Preallocate objects, so we won't count gc time." >>>>> n := 1000000. >>>>> objects := Array new: n streamContents: [ :stream | >>>>> n timesRepeat: [ stream nextPut: Object new ] ]. >>>>> >>>>> set := IdentitySet new: n. >>>>> Smalltalk garbageCollect. >>>>> [1 to: n do: [ :i | set add: (objects at: i) ] ] timeToRun. "4949" >>>>> >>>>> set := LargeIdentitySet new. >>>>> Smalltalk garbageCollect. >>>>> [1 to: n do: [ :i | set add: (objects at: i) ] ] timeToRun. "331" >>>>> >>>>> set := (PluggableSet new: n) >>>>> hashBlock: [ :object | object identityHash * 4096 + object class >>>>> identityHash * 64 ]; "Change this to #basicIdentityHash in Pharo" >>>>> equalBlock: [ :a :b | a == b ]; >>>>> yourself. >>>>> Smalltalk garbageCollect. >>>>> [1 to: n do: [ :i | set add: (objects at: i) ] ] timeToRun. "5511" >>>>> >>>>> >>>>> I also have a LargeIdentityDictionary, which is relatively fast, but >>>>> not >>>>> as fast as LargeIdentitySet, because (for some unknown reason) we don't >>>>> have a primitive that could support it. If we had a primitive like >>>>> primitive 132 which would return the index of the element if found or >>>>> 0 if >>>>> not, then we could have a really fast LargeIdentityDictionary. >>>>> >>>>> >>>>> Levente >>>>> >>>>> Hehe yes, if writing a version fully exploiting the limited range, >>>> that's >>>> probably the approach I would go for as well. >>>> (IAssuming it's the version at http://leves.web.elte.hu/** >>>> squeak/LargeIdentitySet.st<htt**p://leves.web.elte.hu/squeak/** >>>> LargeIdentitySet.st<http://leves.web.elte.hu/squeak/LargeIdentitySet.st> >>>> > >>>> ) >>>> >>>> Mariano commented in the version at http://www.squeaksource.com/** >>>> FuelExperiments <http://www.squeaksource.com/**FuelExperiments<http://www.squeaksource.com/FuelExperiments>> >>>> that it's >>>> >>>> slow for them, which I guess is due to not adopting #identityHash calls >>>> to >>>> #basicIdentityHash calls for Pharo: >>>> ((0 to: 4095) collect: [:each | each << 22 \\ 4096 ]) asSet size -> 1 >>>> So it basically uses 1 bucket instead of 4096... Whoops. :) >>>> >>>> Uploaded a new version to the MC repository which is adapted for Pharo, >>>> on the same machine my numbers were taken from, it does the same test >>>> as I >>>> used above in 871 ms. (181 with preallocation). >>>> >>>> >>> Cool. One more thing: in Squeak the method using primitive 132 directly >>> was renamed to #instVarsInclude:, so now #pointsTo: works as expected. If >>> this was also added to Pharo, then the #pointsTo: sends should be changed >>> to #instVarsInclude:, otherwise Array can be reported as included even if >>> it wasn't added. >>> I'll upload my LargeIdentityDictionary implementation to the same place >>> this evening, since it's still 2-3 factor faster than other solutionts >>> and >>> there seem to be demand for it. >>> >>> >>> Levente >>> >>> >>> Cheers, >>>> Henry >>>> >>>> >>>> >>>> >>> >> >> -- >> Mariano >> http://marianopeck.wordpress.**com <http://marianopeck.wordpress.com> >> >> > -- Mariano http://marianopeck.wordpress.com

3 5

Help needed: old issues issue tracker entries
by marcus.denker＠inria.fr Dec. 9, 2015

Dec. 9, 2015

Hi, The issue tracker has 658 open issues. This number is more or less constant. We are fixing and integrating *a lot*, alone the last 7 days we managed to close 89 issue tracker entries. But the older entries see not much work. Of course one reason is that everything fixable gets fixed and only hard cases remainâ¦ but cases can be âdifficultâ for many reasons. I would be nice if everyone could help and have a look at older issues: -> Still relevant? -> Maybe already fixed? -> Is the description good? -> What is the next action that needs to be done? And keep in mind that the issue tracker is not a TODO list. If you see something odd and put and issue âoh, this looks oddâ but there is no action for a year, does it really make sense to keep that issue open? Every open issue takes energy away from the others. So please check if issues make sense of this kind: -> âIt would be nice ifâ but not even important enough for the submitter to do -> TODO issues that are huge projects in themselves -> â¦. It would be nice if *you* would check the issue that you have been involved with the last months and see what is needed to solve them. Marcus

9 11

Java Future
by S Krish Dec. 6, 2015

Dec. 6, 2015

*Opportunities.. for Pharo..* *The email, sent to InfoWorld on Tuesday by a former high-ranking Java official, claimed to feature details from inside Oracle. It said the company was becoming a cloud company, competing with Salesforce, and âJava has no interest to them anymore.â The subject line cited âJava â planned obsolescence.â* *Oracle is not interested in empowering its competitors and doesnât want to share innovation, the email further alleges. The company is slimming down Java EE (Enterprise Edition), but it also doesnât want anyone else to work on Java or Java EE and is sidelining the JCP (Java Community Process). âThey have a winner-take-all mentality and they are not interested in collaborating,â said the email. âProprietary product work will be done on WebLogic, and thereâll be a proprietary microservices platform.â WebLogic is the Java application server Oracle acquired when it bought BEA Systems in 2008.* https://dzone.com/articles/even-if-oracle-is-losing-interest-in-java-should…

13 20

vm crash in SmalltalkImage>garbageCollect
by Andrei Chis Dec. 3, 2015

Dec. 3, 2015

Hi, With both the latest and stable vm I have an use case in which the vm crashed in SmalltalkImage>>garbageCollect. To set up an image that exhibits the failure , execute this with the latest pharo version: /pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]." ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main ConfigurationOfGToolkitCore --install=3.2 Then attempting to run the following code triggers the failure: ./pharo Pharo.image eval --save "TestRunner open model packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate: 'GTInspectorExamplesTest'; runAll" Based on the trace below the failure happens when the test GTInspectorExamplesTest calls 'Smalltalk>>garbageCollect' in the setUp method. That call can be removed, however, in other runs the failure happens in other methods calling Smalltalk>>garbageCollect. Is it possible that this is a bug with the image (some broken object) or is it a vm bug? Cheers, Andrei andrei$ ./pharo Pharo.image eval --save "{ { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }. { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }. { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTEventRecorder'. 'Moose'. 'GToolkit' }. { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }. } do: [ :spec | Gofer new smalltalkhubUser: spec second project: spec third; package: spec first; load ]." andrei$ ./pharo Pharo.image config http://www.smalltalkhub.com/mc/Pharo/Pharo50Inbox/main ConfigurationOfGToolkitCore --install=3.2 andrei$ ./pharo Pharo.image eval --save "TestRunner open model packageSearchUpdate: 'gt-tests-inspector'; classSearchUpdate: 'GTInspectorExamplesTest'; runAll" Segmentation fault Mon Nov 23 16:48:36 2015 https://github.com/pharo-project/pharo-vm.git Commit: 28d077d8df494ce050ca42c97c892471e8b8740c Date: 2015-10-16 12:02:43 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #15016 C stack backtrace: 0 Pharo 0x0004cacf reportStackState + 159 Smalltalk stack dump: 0xbffbf1a0 M SmalltalkImage>garbageCollect 0x1fd49e30: a(n) SmalltalkImage 0xbffbf1c0 I GTInspectorExamplesTest>setUp 0x2126bc80: a(n) GTInspectorExamplesTest 0x2126cb90 is not a context Most recent primitives @ basicNew @ @ @ @ @ @ @ @ @ basicNew basicNew basicNew @ @ @ @ shallowCopy new new: new: basicNew basicNew new: basicNew new: replaceFrom:to:with:startingAt: new: basicNew new: replaceFrom:to:with:startingAt: new: basicNew @ new: at:put: at:put: perform:with: perform:with: perform: @ @ basicNew @ @ @ @ @ @ basicNew @ new: at:put: at:put: perform:with: perform:with: perform: @ @ basicNew @ @ @ @ @ @ new @ @ @ @ @ basicNew @ @ new: at:put: @ @ basicNew @ @ @ @ new: at:put: at:put: at:put: at:put: new: @ at:put: @ at:put: @ at:put: @ at:put: @ @ @ @ @ @ basicNew @ @ basicNew @ @ basicNew @ @ @ @ @ shallowCopy shallowCopy @ @ new: at:put: at:put: at:put: at:put: new: @ at:put: @ at:put: @ at:put: @ at:put: @ @ @ @ @ @ basicNew @ @ basicNew @ @ basicNew @ @ @ @ @ basicNew @ @ @ @ basicNew @ @ basicNew @ @ basicNew @ @ @ @ @ basicNew @ @ @ @ basicNew @ @ perform: basicNew new: basicNew new: basicNew new: shallowCopy shallowCopy primUTCMicrosecondsClock // basicNew basicNew new: at:put: at:put: at:put: at:put: value valueNoContextSwitch basicNew new: basicNew new: new: basicNew new: replaceFrom:to:with:startingAt: primitiveGarbageCollect **IncrementalGC** **FullGC** garbageCollectMost **IncrementalGC** basicNew new: someInstance basicNew new: someInstance basicNew new: someInstance new: basicNew new: replaceFrom:to:with:startingAt: primitiveGarbageCollect **IncrementalGC** **FullGC** garbageCollectMost **IncrementalGC** wait shallowCopy shallowCopy signal wait shallowCopy shallowCopy at:put: at:put: at:put: at:put: at:put: at:put: signal wait shallowCopy shallowCopy at:put: at:put: signal new: basicNew new: replaceFrom:to:with:startingAt: primitiveGarbageCollect **IncrementalGC** **FullGC** (Segmentation fault) ./pharo: line 11: 5224 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" --headless "$@"

4 21

Digest from slack to the mailing list?
by Stephan Eggermont Dec. 3, 2015

Dec. 3, 2015

Should we have a digest from slack to a mailing list? We are already losing messages Stephan

10 16

GTools merging configurations
by Andrei Chis Dec. 1, 2015

Dec. 1, 2015

Hi, For the GTInspector, GTPlayground and GTSpotter we now have distinct configurations. However, this complicates the integration process with Pharo as a lot of configurations need to be updated. So we'd like to merge them in ConfigurationOfGToolkitCore. What do you think? This will simplify a lot the integration process. Cheers, Andrei

5 5

what happened to the monkey
by Nicolai Hess Dec. 1, 2015

Dec. 1, 2015

no issue validation since last weekend.

4 4

Dec. 1, 2015

Greetings! We're thinking to power up Pharo with some machine learning algorithms (Naive Bayes, Random Forest and so on). I'm wondering if there is anything done already? Thanks, KlÃ©risson

3 2

Playing video
by J.F. Rick Nov. 30, 2015

Nov. 30, 2015

Is there a way to play a video file (MP4, AVI, etc.) in Pharo for Mac? There used to be a way to do this in Squeak but I can't find any documentation of how I might do it in Pharo.

1 0

Unable to open context-menu in debugger inspector (Pharo 5)
by Esteban A. Maringolo Nov. 30, 2015

Nov. 30, 2015

When I try to open the context menu in a workspace (not Playground) or in the code pane of an inspector I get the following: When I debug I get the following exception: "MessageNotUnderstood: MorphicTextAdapter>>acceptAllowed" The image is Pharo-5.0-50473 Regards! Esteban A. Maringolo ps: Stack trace MorphicTextAdapter(Object)>>doesNotUnderstand: #acceptAllowed RubPlainTextMode class>>menuOn: [ prg methodClass theNonMetaClass perform: prg selector with: menu ] in [ :prg | self currentRoot: self while: [ prg methodClass theNonMetaClass perform: prg selector with: menu ] ] in PragmaMenuBuilder>>collectRegistrations in Block: [ prg methodClass theNonMetaClass perform: prg sel...etc... [ aBlock value ] in PragmaMenuBuilder>>currentRoot:while: in Block: [ aBlock value ] BlockClosure>>ensure:

2 3