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

Re: [Pharo-project] Issue 3345 in pharo: findBinary: from Cuis as integrated in Squeak

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3950 Comment #1 on issue 3345 by marcus.d...(a)gmail.com: findBinary: from Cuis as integrated in Squeak http://code.google.com/p/pharo/issues/detail?id=3345 Pls Discuss in Issue 3950

April 5, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Camillo Bruni

On 2011-04-05, at 15:02, Nicolas Cellier wrote: > Better than average, take the median NO! thats why you provide the standard deviation... you should not optimize the results prematurely but provide numbers that let you decide on the quality of the benchmarks. what you can do is optimize for systematic errors, like warm up and stuff, but nevertheless you should provide the raw results... read the paper... > Nicolas > > 2011/4/5 Camillo Bruni <camillo.bruni(a)inria.fr>: >> This is exactly why you have to provide some confidence interval / deviation, otherwise it is hard to make any reasonable conclusion. >> >> run it 100 times and take the average and provide the standard deviation. >> >> I am not a big fan of relying on incomplete benchmarking results: >> >> Please read: http://portal.acm.org/citation.cfm?id=1297033 >> >> http://www.squeaksource.com/p.html provides a basic benchmarking framework under the NBenchmark package. You subclass from PBenchmarkSuite implement a method #benchXXX and run it. >> >> r := PBFloat run: 100. >> r asString >> >> which will give decent results back :). This way it is much easier to make sense out of the numbers. >> >> So here again to remember: >> >> - number of samples >> - average run times >> - standard deviation >> >> If one of these results is missing the benchmark results are incomplete. >> >> best regards, >> camillo >> >> >> >> On 2011-04-05, at 13:56, Igor Stasenko wrote: >> >>> VariableNode initialize. >>> Compiler recompileAll. >>> >>> [ >>> TestCase allSubclasses do: [ :cls| >>> cls isAbstract >>> ifFalse: [cls suite run]]. >>> ] timeToRun >>> >>> 178938 >>> 183963 >>> >>> >>> >>> (ParseNode classVarNamed: 'StdSelectors') removeKey: #class ifAbsent: []. >>> Compiler recompileAll. >>> >>> [ >>> TestCase allSubclasses do: [ :cls| >>> cls isAbstract >>> ifFalse: [cls suite run]]. >>> ] timeToRun >>> >>> 187168 >>> 184992 >>> >>> the deviation is too big to see if its really so big overhead. >>> >>> if you compare worst , you got 187/178 ~ 5% >>> and if you compare the best you got >>> 184/183 ~ 0.5% >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> >

April 5, 2011

Re: [Pharo-project] Issue 3942 in pharo: Transcript missing compatibility method ensureCr

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3942 by marcus.d...(a)gmail.com: Transcript missing compatibility method ensureCr http://code.google.com/p/pharo/issues/detail?id=3942 in 13132

April 5, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Nicolas Cellier

Better than average, take the median Nicolas 2011/4/5 Camillo Bruni <camillo.bruni(a)inria.fr>: > This is exactly why you have to provide some confidence interval / deviation, otherwise it is hard to make any reasonable conclusion. > > run it 100 times and take the average and provide the standard deviation. > > I am not a big fan of relying on incomplete benchmarking results: > > Please read: http://portal.acm.org/citation.cfm?id=1297033 > > http://www.squeaksource.com/p.html provides a basic benchmarking framework under the NBenchmark package. You subclass from PBenchmarkSuite implement a method #benchXXX and run it. > > r := PBFloat run: 100. > r asString > > which will give decent results back :). This way it is much easier to make sense out of the numbers. > > So here again to remember: > > - number of samples > - average run times > - standard deviation > > If one of these results is missing the benchmark results are incomplete. > > best regards, > camillo > > > > On 2011-04-05, at 13:56, Igor Stasenko wrote: > >> VariableNode initialize. >> Compiler recompileAll. >> >> [ >> TestCase allSubclasses do: [ :cls| >> Â Â Â Â cls isAbstract >> Â Â Â Â Â Â Â Â ifFalse: [cls suite run]]. >> ] timeToRun >> >> 178938 >> 183963 >> >> >> >> (ParseNode classVarNamed: Â 'StdSelectors') removeKey: #class ifAbsent: []. >> Compiler recompileAll. >> >> [ >> TestCase allSubclasses do: [ :cls| >> Â Â Â Â cls isAbstract >> Â Â Â Â Â Â Â Â ifFalse: [cls suite run]]. >> ] timeToRun >> >> 187168 >> 184992 >> >> the deviation is too big to see if its really so big overhead. >> >> if you compare worst , you got Â 187/178 ~ 5% >> and if you compare the best you got >> 184/183 Â ~ 0.5% >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > >

April 5, 2011

Re: [Pharo-project] Issue 3961 in pharo: Fix order of worlmenu

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3961 by marcus.d...(a)gmail.com: Fix order of worlmenu http://code.google.com/p/pharo/issues/detail?id=3961 in 13132

April 5, 2011

Re: [Pharo-project] Issue 3963 in pharo: RPackageOrganizer and announcements

by pharo＠googlecode.com

Comment #1 on issue 3963 by marcus.d...(a)gmail.com: RPackageOrganizer and announcements http://code.google.com/p/pharo/issues/detail?id=3963 Issue 3937 has been merged into this issue.

April 5, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Camillo Bruni

This is exactly why you have to provide some confidence interval / deviation, otherwise it is hard to make any reasonable conclusion. run it 100 times and take the average and provide the standard deviation. I am not a big fan of relying on incomplete benchmarking results: Please read: http://portal.acm.org/citation.cfm?id=1297033 http://www.squeaksource.com/p.html provides a basic benchmarking framework under the NBenchmark package. You subclass from PBenchmarkSuite implement a method #benchXXX and run it. r := PBFloat run: 100. r asString which will give decent results back :). This way it is much easier to make sense out of the numbers. So here again to remember: - number of samples - average run times - standard deviation If one of these results is missing the benchmark results are incomplete. best regards, camillo On 2011-04-05, at 13:56, Igor Stasenko wrote: > VariableNode initialize. > Compiler recompileAll. > > [ > TestCase allSubclasses do: [ :cls| > cls isAbstract > ifFalse: [cls suite run]]. > ] timeToRun > > 178938 > 183963 > > > > (ParseNode classVarNamed: 'StdSelectors') removeKey: #class ifAbsent: []. > Compiler recompileAll. > > [ > TestCase allSubclasses do: [ :cls| > cls isAbstract > ifFalse: [cls suite run]]. > ] timeToRun > > 187168 > 184992 > > the deviation is too big to see if its really so big overhead. > > if you compare worst , you got 187/178 ~ 5% > and if you compare the best you got > 184/183 ~ 0.5% > > > -- > Best regards, > Igor Stasenko AKA sig. >

April 5, 2011

Re: [Pharo-project] Issue 3937 in pharo: Breaking Announcement system

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3963 Comment #1 on issue 3937 by marcus.d...(a)gmail.com: Breaking Announcement system http://code.google.com/p/pharo/issues/detail?id=3937 (No comment was entered for this change.)

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by StÃ©phane Ducasse

I ill have a look when I get a little moment. Stef On Apr 5, 2011, at 9:19 AM, Sven Van Caekenberghe wrote: > > On 05 Apr 2011, at 07:09, laurent laffont wrote: > >> Remarks: >> - group changed by categories: Morphic/Polymorph, Tools, Under the hood, ... >> - Mocketry is not included in Pharo 1.2 > > > Thanks for the feedback, I applied your suggestions. And uploaded a newer version. > > More comments ? > > Sven

April 5, 2011

[Pharo-project] Issue 3963 in pharo: RPackageOrganizer and announcements

by pharo＠googlecode.com

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Nautilus Milestone-1.3 New issue 3963 by Benjamin...(a)gmail.com: RPackageOrganizer and announcements http://code.google.com/p/pharo/issues/detail?id=3963 I propose a workable solution in PharoTaskForces: Name: SystemAnnouncements-BenjaminVanRyseghem.38 Author: BenjaminVanRyseghem Time: 5 April 2011, 2:41:14 pm UUID: 157eabfb-9f1c-4986-8006-fb961e2414d2 Ancestors: SystemAnnouncements-cyrilledelaunay.37 New version with InternalAnnouncement for RPackage ------------------------------------------------ Name: RPackage-Core-BenjaminVanRyseghem.70 Author: BenjaminVanRyseghem Time: 5 April 2011, 2:42:04 pm UUID: 7a56fce7-ef8d-491a-8746-aede3e9e22c4 Ancestors: RPackage-Core-BenjaminVanRyseghem.69 Announcements are sent when RPackages are modified ------------------------------------------------ Name: RPackage-SystemIntegration-BenjaminVanRyseghem.52 Author: BenjaminVanRyseghem Time: 5 April 2011, 2:44:19 pm UUID: 78b4ec5e-742b-45b5-8f2e-56886c5f2f8e Ancestors: RPackage-SystemIntegration-cyrilledelaunay.51 Now registered to InternalAnnouncements to execute during integration: Pre: RPackageOrganizer allInstances do: [:each | SystemAnnouncer announcer unsubscribe: each]. Post: RPackageOrganizer allInstances do: [:each | each RPackageOrganizer default registerInterestToSystemAnnouncement]

April 5, 2011