- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.1] #11284

by Marcus Denker

#11284 ====== Hashed collection performance improvement, phase 4 of 4. Changes identityHash to cover most of the positive SmallInteger range, and uses good prime table sizes. This makes large hashed collections much faster, and does not penalize the small ones. Targeted at Pharo Core 1.1-11280 Load the slice for each phase in order. Allow maybe half an hour to load all four phases; the intermediate phases load very slowly due to existing hashed collections running in "slow but safe" mode while their hash function changes under them. In phase 4: * All of the scanFor: methods modified in phase 1 are loaded into their final form (sometimes a revert to original) which does not scan the entire table before giving up. * The rehashing class and temporary methods are removed, having done their job at the end of phase 3. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 22, 2010

[Pharo-project] [update 1.1] #11283

by Marcus Denker

#11283 ====== Hashed collection performance improvement, phase 3 of 4. Changes identityHash to cover most of the positive SmallInteger range, and uses good prime table sizes. This makes large hashed collections much faster, and does not penalize the small ones. Targeted at Pharo Core 1.1-11280 Load the slice for each phase in order. Allow maybe half an hour to load all four phases; the intermediate phases load very slowly due to existing hashed collections running in "slow but safe" mode while their hash function changes under them. In phase 3: * Identity hash values are changed. * Set>>growSize, rendered obsolete by phase 2, is removed. * A "Rehasher" class is added * Rehasher class>>initialize rehashes all hashed collections. Phase 3 takes several minutes to load, due to load and rehashing taking place in "slow but safe" mode. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 22, 2010

[Pharo-project] [update 1.1] #11282

by Marcus Denker

#11282 ====== Hashed collection performance improvement, phase 2 of 4. Changes identityHash to cover most of the positive SmallInteger range, and uses good prime table sizes. This makes large hashed collections much faster, and does not penalize the small ones. Targeted at Pharo Core 1.1-11280 Load the slice for each phase in order. Allow maybe half an hour to load all four phases; the intermediate phases load very slowly due to existing hashed collections running in "slow but safe" mode while their hash function changes under them. In phase 2: * All methods that will ultimately need to send #basicIdentityHash are modified to do so. * Hashed collections now choose their table sizes to be prime using the HashTableSizes class loaded in phase 1. * Hashed collections are made cautious but slow. They will continue to operate even when their hashing is broken, as it will be during part of the loading of phase 3. This caution will be removed in phase 4. Loading phase 2 may take several minutes due to the cautious hashed collection slowdown. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 22, 2010

[Pharo-project] [update 1.1] #11281

by Marcus Denker

#11281 ---------- Changes identityHash to cover most of the positive SmallInteger range, and uses good prime table sizes. This makes large hashed collections much faster, and does not penalize the small ones. Targeted at Pharo Core 1.1-11280 Load the slice for each phase in order. Allow maybe half an hour to load all four phases; the intermediate phases load very slowly due to existing hashed collections running in "slow but safe" mode while their hash function changes under them. In phase 1: * Methods and classes that will be referenced in phase 2 are added. This includes #basicIdentityHash and the size-selecting class. * No behavior is changed yet. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 22, 2010

Re: [Pharo-project] How I build squeak-vm with FT2Plugin on Linux

by Mariano Martinez Peck

On Mon, Mar 22, 2010 at 9:22 PM, Bryce Kampjes <bryce(a)kampjes.demon.co.uk>wrote: > On Thu, 2010-03-11 at 10:28 +0100, Mariano Martinez Peck wrote: > > Both really interesting posts. Now...Some people reported that the > > Exupery Linux VM has "nicer" fonts than the standard VM, even if both > > use true type. > > Then Bryce Kampjes said in the mailing list: > > > > "If it's font related then the Exupery VMs also have a patched bitlbt > > for > > subpixel antialiasing. The true type code uses that to make fonts look > > a > > bit nicer." > > > > Do you know how that can be included ? > > Apply the .cs in the following email to your copy of VMMaker and also > build the truetype plugin: > > > http://n4.nabble.com/Fwd-Pharo-project-New-Pharo-based-on-core-10309-with-a… > > The truetype work was done by Andy Tween. Googling for him, truetype, > plugin, and VM should find a bit more information. > > Thanks Bryce!!! would be cool to have the "official" Linux VM for Pharo 1.0 release with this feature. Cheers Mariano Bryce > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 22, 2010

[Pharo-project] Thanks martin :)

by stephane ducasse

hi martin marcus and me integrated your fixes. Marcus should send a nice update mail. Thanks again. Stef (from my bed, got a nice virus from my smallest boy).

March 22, 2010

Re: [Pharo-project] Implementing MethodWrappers in Smalltalk

by Alexandre Bergel

Hi Mariano, I worked on a similar problem for a new code profiler. Spy is a framework for easily performing program execution analysis. A short tutorial, screenshots, and some examples are available on: http://www.moosetechnology.org/tools/Spy If you're working in that direction, I would be delighted to collaborate. Cheers, Alexandre On 22 Mar 2010, at 12:51, Mariano Martinez Peck wrote: > Hi folks. I was reading the PBE chapter about reflection where it > talks a little about Method Wrappers. Then, I took a look at > TestCoverage implementation. > > After that, I took a look at http://www.squeaksource.com/ObjectsAsMethodsWrap > > The main difference between both approaches are: > > TestCoverage > - Just extends from ProtoObject, implement doesNotUnderstand: , > run: aSelector with: anArray in: aReceiver , etc > - To install and uninstall the wrappers uses methodDictionary at: > xxx put: yyy > - Just for test coverage. > > ObjectAsMethodWrapper > - Is more generic, support pre and post closures, and you can > subclass and create you own wrapper > - To install and uninstall the wrappers it uses Class >> > addSelector: self selector withMethod: self > > So...what I did ?? I created a TestCoverage but creating a subclass > of ObjectAsMethodWrapper called TestCoverageMethodWrapper which > just implements a 1 or 2 methods. I mean, I reused the generic > ObjectAsMethodWrapper. It seems to work ok. > > I did some test running TestCoverage with both implementation and it > seems mine (TestCoverageMethodWrapper) is 30% much slower than the > original. > Trying to understand why, I think it is because the original one > uses just methodDictionary at: xxx put: yyy > but mine uses Class >> addSelector: self selector withMethod: self. > In this last method, there are all the notifications, add to > localSelectors...etc > > Now...I have two questions: > > 1) For a generic approach to method wrappers, which of those two > ways would you use ? should I care about notifying, adding to > localSelectors, etc? Or at is just temporal, I don't care ? > which are the pros and cons you see with each alternative ? > > 2) Do you think it make sense to the package ObjectsAsMethodsWrap > in PharoCore as a "library" to create lightweight proxies ? It is > just 4 classes and it would be cool to change TestCoverage to that > implementation. Then, you only don't have the library, but also some > real examples. Of course, this can be done if we eleiminate the 30% > of slowleness. > > > so...what do you think ? > > Cheers > > Mariano > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 22, 2010

Re: [Pharo-project] How I build squeak-vm with FT2Plugin on Linux

by Bryce Kampjes

On Thu, 2010-03-11 at 10:28 +0100, Mariano Martinez Peck wrote: > Both really interesting posts. Now...Some people reported that the > Exupery Linux VM has "nicer" fonts than the standard VM, even if both > use true type. > Then Bryce Kampjes said in the mailing list: > > "If it's font related then the Exupery VMs also have a patched bitlbt > for > subpixel antialiasing. The true type code uses that to make fonts look > a > bit nicer." > > Do you know how that can be included ? Apply the .cs in the following email to your copy of VMMaker and also build the truetype plugin: http://n4.nabble.com/Fwd-Pharo-project-New-Pharo-based-on-core-10309-with-a… The truetype work was done by Andy Tween. Googling for him, truetype, plugin, and VM should find a bit more information. Bryce

March 22, 2010

Re: [Pharo-project] RC3 - small stuff

by Schwab,Wilhelm K

Dale, Another project that Citezen might need is Rio. It looks like Damien has been busy. The ConfigurationOfCitezen is in the repository. For fun, I tried Gofer project load:'Citezen' and get an error "No versions matching version (latest)" I am not sure whether this is something that I should stop nagging and let Damien fix, or if I'm not doing this correctly. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Dale Henrichs Sent: Monday, March 22, 2010 2:18 PM To: Pharo-project(a)lists.gforge.inria.fr Cc: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] RC3 - small stuff Bill, Looks like ConfgurationOfCitezen does need required projects added (I am willing to help the maintainers - drop me a line). Perhaps the configs aren't ready for prime time and that's why they have not been added to MetacelloRepository. You can add repositories to your own GoferProject: Gofer project repository: 'Repository URL'. Will add another repository to the search path. Dale ----- "Wilhelm K Schwab" <bschwab(a)anest.ufl.edu> wrote: | Hello all, | | Some time ago, there was (I thought) a patch for saving workspace text | to a file; I had hoped to find that in 1.0, but it is not in RC3 that | I can find. | | The first thing I did was load the Loader extensions to Gofer. It | installed as expected. I have not looked into the code, but tried | #search: and found things like Citezen and Rio missing. That might be | "simply" because the Configuration* packages are not in the Metacello | repository?? If so, are they not there for a non-trivial reason? | | I then grabbed ConfigurationOfCitezen, and was hung up by an | unsatisfied dependence on SmaCC. The SmaCC runtime is in my RC1 image, | but I don't know how/why it was loaded; presumably CZLoader did it. | | Are these bugs or features? I am leaning toward bugs, but the | question is whether any or all of the following appicable: (1) | ConfigurationOfCitezen needs to load prerequisites; (2) Loader is in | the wrong to not see them; (3) I need to add repositories to Loader; | (4) various ConfigurationOf* packages need to be in the Metacello | repository. | | Any ideas? | | Bill | | | _______________________________________________ | 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

March 22, 2010

Re: [Pharo-project] RC3 - small stuff

by Schwab,Wilhelm K

Chris, Understood, but somebody created what I thought was a correct patch to add something to the workspace menu to do it, and it would be a shame to lose it. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Chris Muller Sent: Monday, March 22, 2010 1:59 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] RC3 - small stuff Hi Bill, I think you can just create a new file in the file-list, cut and paste your WS into it, save again.. On Mon, Mar 22, 2010 at 1:16 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Hello all, > > Some time ago, there was (I thought) a patch for saving workspace text to a file; I had hoped to find that in 1.0, but it is not in RC3 that I can find. > > The first thing I did was load the Loader extensions to Gofer. Â It installed as expected. Â I have not looked into the code, but tried #search: and found things like Citezen and Rio missing. Â That might be "simply" because the Configuration* packages are not in the Metacello repository?? Â If so, are they not there for a non-trivial reason? > > I then grabbed ConfigurationOfCitezen, and was hung up by an unsatisfied dependence on SmaCC. The SmaCC runtime is in my RC1 image, but I don't know how/why it was loaded; presumably CZLoader did it. > > Are these bugs or features? Â I am leaning toward bugs, but the question is whether any or all of the following appicable: (1) ConfigurationOfCitezen needs to load prerequisites; (2) Loader is in the wrong to not see them; (3) I need to add repositories to Loader; (4) various ConfigurationOf* packages need to be in the Metacello repository. > > Any ideas? > > Bill > > > _______________________________________________ > 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

March 22, 2010