May 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-fuel] (Identity)Dictionary benchmarks

by Stefan Marr

Hi Martin: On 21 May 2013, at 14:31, Martin Dias <tinchodias(a)gmail.com> wrote: > BTW, does SMark provide a way to write ad-hoc bechmarks in the > workspace, without creating a bench* method in a benchmark class? > > I mean something like: > > [ 1000 factorial ] bench > > but with the power of smark No, it doesn't currently. But if you care enough to implement it, you'll probably want to have a tool class that has a benchDoIt method, which in its body just sends #value to the block. Patches welcome ;) Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

May 21, 2013

Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31

by Tudor Girba

What is LightHouse? :) Doru On Tue, May 21, 2013 at 2:14 PM, Gareth Cox <gareth(a)inspired.org> wrote: > ### Here's what I've been up to since the last WhatsUp: > > LightHouse > -Learning Glamour > -Started new project with Stephan Eggermont and Diego Lont as part of GSoC. > Project is a Distributed Issue Tracker built in Pharo for Pharo! > ( > https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/riv… > ) > > > ### What's next, until 2013-05-31 (*): > > LightHouse > -More Learning Glamour > -More working on LightHouse UI > > Dusty > -- www.tudorgirba.com "Every thing has its own flow"

May 21, 2013

Removing a package from Smalltalkhub

by roberto.minelli＠usi.ch

Hi, I was wondering if and how can I delete a package from Smalltalkhub. Thanks in avance, R

May 21, 2013

Removing a package from Smalltalkhub

by Roberto Minelli

Hi, I was wondering if and how can I delete a package from Smalltalkhub. Thanks in avance, R

May 21, 2013

Re: [Pharo-dev] [sbe] Pharo por Ejemplo vs Pharo en exemplos

by Esteban A. Maringolo

+uno a "Pharo en ejemplos" ;-) Regards! Esteban A. Maringolo 2013/5/21 Rafael Luque <rafael.luque.leiva(a)gmail.com> > I contributed to this translation with the Syntax and Seaside chapters. > IMO "Pharo en Ejemplos" sounds more natural than "Pharo por Ejemplo" that > is the literal word-by-word translation. > > Rafa > > > 2013/5/21 stephane ducasse <stephane.ducasse(a)free.fr> > >> >> On May 21, 2013, at 8:47 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: >> >> > >> > Be careful, there are many different forms of Spanish. The title should >> be consistent with the main text. We are not qualified to judge. Ask >> someone who knows the different dialects. >> >> >> Yes I know :) >> >> > >> > Oscar >> > >> > --- >> > Prof. Dr. O. Nierstrasz -- oscar(a)iam.unibe.ch >> > Software Composition Group -- http://scg.unibe.ch/oscar >> > University of Bern -- Tel/Fax +41 31 631.4618/3355 >> > >> > >> > On 2013-05-21, at 8:18, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> wrote: >> > >> >> Hi guys >> >> >> >> one guy mentions that Pharo en exemplos is a better translation than >> Pharo por Ejemplo so what is your point of view on that? >> >> >> >> Stef >> >> _______________________________________________ >> >> sbe mailing list >> >> sbe(a)iam.unibe.ch >> >> https://www.iam.unibe.ch/mailman/listinfo/sbe >> > >> > _______________________________________________ >> > sbe mailing list >> > sbe(a)iam.unibe.ch >> > https://www.iam.unibe.ch/mailman/listinfo/sbe >> >> >> >

May 21, 2013

Re: [Pharo-dev] [Pharo-fuel] (Identity)Dictionary benchmarks

by Martin Dias

>> a) your benchmarking script sucks! => use SMARK!! http://smalltalkhub.com/#!/~StefanMarr/SMark > > We're fully aware of that :) > :) in the todo list BTW, does SMark provide a way to write ad-hoc bechmarks in the workspace, without creating a bench* method in a benchmark class? I mean something like: [ 1000 factorial ] bench but with the power of smark

May 21, 2013

Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31

by Gareth Cox

### Here's what I've been up to since the last WhatsUp: LightHouse -Learning Glamour -Started new project with Stephan Eggermont and Diego Lont as part of GSoC. Project is a Distributed Issue Tracker built in Pharo for Pharo! (https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/riv…) ### What's next, until 2013-05-31 (*): LightHouse -More Learning Glamour -More working on LightHouse UI Dusty

May 21, 2013

[update 3.0] #30151

by Esteban Lorenzano

30151 ----- 5562 rename Morphic package to Morphic-Base https://pharo.fogbugz.com/f/cases/5562 old one, hard one :)

May 21, 2013

Re: [Pharo-dev] Zinc problem with PUT requests

by Nicolas Petton

Thanks sven, I'll try it later today. Nico On May 21, 2013, at 1:01 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi Damien, > > On 21 May 2013, at 10:20, Damien Cassou <damien.cassou(a)gmail.com> wrote: > >> It looks like Zinc has a problem handling PUT requests (at least >> ZnZincServerAdaptor). If I replace ZnZincServerAdaptor by WAKom, then >> things work fine. To reproduce: >> >> Setting up the Server >> 1- Download a SmalltalkHub image >> (https://ci.inria.fr/pharo-contribution/job/SmalltalkHub/) >> 2- Install mongodb on your computer (for Debian: apt-get install mongodb) >> 3- Launch the SmalltalkHub image >> 4- Evaluate: ZnZincServerAdaptor startOn: 8080 >> 5- Visit http://localhost:8080/tools/hub, create an account and a project >> >> Setting up the Client >> 6- In a different image, start monticello >> 7- add the repository of your new project to Monticello (something >> like http://localhost:8080/mc/YourUser/YourProject/main) don't forget >> the username and password >> 8- copy an existing package of your cache to the new repository >> >> You will get an error in the client: a ZnStringEntity(text/plain 512B >> file is too short) >> >> If you install Seaside-Adaptors-Kommanche and use WAKom, things will >> work just fine. >> >> You can configure Seaside to open a server-side error: just setup the >> WAExceptionFilter to WADebugErrorHandler in >> http://localhost:8080/config/mc >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill > > Thanks for the detailed instructions, now I have StHub & mongo running on my machine ;-) > > The problem you reported can easily be fixed by loading the latest version of Zinc-Seaaside (the one in the StHub image is very old). Now, it still does not fully work, but I don't understand all the Sh and MA stuff, I am afraid. > > But if you go up the stack until you find Seaside's aRequestContext and find the request body in it (the data which was PUT), you can do > > (ZipArchive new readFrom: self asByteArray readStream) members > > on it, so for me that means the data arrives OK. > > If you have another problem with the Zinc/Adaptor part, please let me know. > > HTH, > > Sven > > PS: > > -- Nicolas Petton http://www.nicolas-petton.fr

May 21, 2013

Re: [Pharo-dev] [Pharo-fuel] (Identity)Dictionary benchmarks

by Max Leske

On 21.05.2013, at 10:58, Camillo Bruni <camillobruni(a)gmail.com> wrote: > my random pessimistic comments > > a) your benchmarking script sucks! => use SMARK!! http://smalltalkhub.com/#!/~StefanMarr/SMark We're fully aware of that :) > b) check my master thesis for a more thorough testing of dictionary, including a cleaner implementation that defaults to something like a small dictionary without a special class: http://scg.unibe.ch/archive/masters/Brun11a.pdf > > the optimistic version: > > > On 2013-05-21, at 09:47, Max Leske <m.leske(a)netstyle.ch> wrote: > >> My coworker performed some interesting benchmarks on the various dictionary types in Pharo. If you look at the attachments you'll see four things: >> 1. SmallDictionary and SmallIdentityDictionary are totally useless when it comes to performance. Unless their existence is somehow justified by saving space (which might be important for embedded systems) I don't see why we should keep them around. > > yes their usage is not always justified, but be careful what you measure: as far as I see you only measure addition, no? (sorry again, but that benchmark brutally sucks, it's so damn hard to read... :P). Iteration and retrieval have to measure as well, also how the dictionaries behave under key hash collisions (though I am definitely not defending the small dicts.. :). > >> 2. The special Fuel collections for large numbers of elements could be a valuable addition to the basic collections > > THere is the pluggable key dictionary for that reason already, no? The main problem is the limited hashes which results in quite some hash collisions for very large dictionaries. > >> 3. SmallInteger>>identityHash is really slow. Using SmallInteger as keys in IdentityDictionary is significantly slower than using them in a regular Dictionary because the identity check is done via #identityHash (#hash simply answers self). > > that is really strange :/ > >> 4. Arrays are cool :) >> >> Should I open issues on FogBugz for any of these points? Especially point 3 bothers me because I feel that using a "primitive" type should be fast under all circumstances. >> >> You'll find below the benchmark data (collected in 1.4, verified in 2.0) and the code to run it. >> >> Cheers, >> Max >> >>> >> <performance.xlsx> >>> >>> >> <performance.xls> >>> >>> >>> >>> >>> >>> -------------------------------------------------------------- >>> >>> ( comments are variations) >>> >>> sizes := #( 10 20 30 40 50 60 70 80 90 100 120 130 140 150 160 170 180 190 200 300 400 500 600 700 800 900 1000 ). >>> "sizes := #( 10 20 30 40 50 60 70 80 90 100 120 130 140 150 160 170 180 190 200 300 400 500 600 700 800 900 1000 1500 2000 2500 3000 3500 4000 4500 5000 6000 7000 8000 9000 10000 )." >>> "batches := sizes collect: [ :size | size -> ((10000000 / size) asFloat // 10) ]." >>> batches := sizes collect: [ :size | size -> 10000 ]. >>> alphabet := Character alphabet. >>> >>> batches do: [ :a | Transcript tab; show: a key asString ]. Transcript cr. >>> batches do: [ :a | Transcript tab; show: a value asString ]. Transcript cr. >>> "{ Dictionary. SmallDictionary. IdentityDictionary. SmallIdentityDictionary. FLLargeIdentityDictionary } " >>> { Dictionary. IdentityDictionary. FLLargeIdentityDictionary } >>> "{ Array }" >>> do: [ :class | >>> Smalltalk garbageCollect. >>> Transcript show: class name. >>> batches >>> do: [ :a | >>> | struct strings iterations | >>> "strings := (1 to: a key) collect: [ :i | i asString ]." >>> strings := (1 to: a key) collect: [ :i | >>> String streamContents: [ :s | >>> 20 atRandom timesRepeat: [ s nextPut: alphabet atRandom ] ] ]. >>> struct := class new. >>> "struct := (class = FLLargeIdentityDictionary >>> ifTrue: [ class new ] >>> ifFalse: [ class new: a key ])." >>> Transcript tab; show: ([ >>> a value timesRepeat: [ >>> 1 to: a key do: [ :i | struct at: (strings at: i)" i" put: i ] ] ] timeToRun). >>> strings := nil ] >>> displayingProgress: class name asString. >>> Transcript cr. ] >>> displayingProgress: 'Processing ...' >>> >> >> _______________________________________________ >> Pharo-fuel mailing list >> Pharo-fuel(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-fuel > > > _______________________________________________ > Pharo-fuel mailing list > Pharo-fuel(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-fuel

May 21, 2013