- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Stack should be reimplemented with Array

by Eliot Miranda

On Mon, Oct 18, 2010 at 1:02 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Eliot > > > There was a post on this list back in August complaining about Stack > inheriting from LinkedList. There was some discussion, but apparently no > resolution, as Stack still inherits from LinkedList in the Pharo 1.2 Core > Image I just downloaded. Rather than reimplementing it to forward to a > contained LinkedList, I think it should use an Array internally like > OrderedCollection does. An Array-based implementation of Stack would be > faster than one based on LinkedList due to the basic stack operations (push, > pop and top) being able to rely more on primitives. This assumes that you > know roughly how a big a stack you need; if you don't, reallocating the > array and copying its contents over and over again will cost you, but this > is an exceptional case;-- most stacks are small and when they aren't, the > programmer usually has enough information to select a reasonable stack size. > > > > *No*. Stack and OrderedCollection differ *usefully*. Adding an item to > a Stack is always O(1). Adding an item to an OrderedCollection is O(N) > because when the array overflows a new one must be allocated and the old > objects copied to the new. Why not apply your speedups to > OrderedCollection, or is that not possible? If not possible, then come up > with a new name and add that. Please /don't/ change Stack. > > I would really like not having Stack inheriting from LinkedList (I hate > subclassing). Now from a VM point of view > is there a constraint that Stack as to be a subclass of LList? > No. The VM doesn't know anything about Stack. > > > > > > > > Enclosed is a fileout of an Array-based Stack implementation. It trounces > the LinkedList-based implementation easily, but more interestingly, it > performs better than an OrderedCollection when used like a stack: > > > > Pushing is roughly ~30% faster: > > r1 :=[100000 timesRepeat: [ > > s := Stack new. > > 10 timesRepeat: [s push: #foo]]] timeToRun. > > r2 := [100000 timesRepeat: [ > > oc := OrderedCollection new. > > 10 timesRepeat: [oc addLast: #foo]]] timeToRun. > > 100 - ((r1 / r2) asFloat * 100). > > > > as is pushing + popping: > > r3 := [100000 timesRepeat: [ > > s := Stack new. > > 10 timesRepeat: [s push: #foo]. > > 10 timesRepeat: [s pop]]] timeToRun. > > r4 := [100000 timesRepeat: [ > > oc := OrderedCollection new. > > 10 timesRepeat: [oc addLast: #foo]. > > 10 timesRepeat: [oc removeLast]]] timeToRun. > > 100 - ((r3 / r4) asFloat * 100). > > _______________________________________________ > > 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 >

Oct. 18, 2010

Re: [Pharo-project] A Lazy Inspector?

by Oscar E A Callau

Thanks Mariano. Now I understand :-) Cheers Ãscar E A Callau On 18 Oct 2010, at 16:52, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > 2010/10/18 Oscar E A Callau <oalvarez(a)dcc.uchile.cl> > > On Oct 18, 2010, at 14:44 , Mariano Martinez Peck wrote: > >> On Mon, Oct 18, 2010 at 4:40 AM, Oscar E A Callau <oalvarez(a)dcc.uchile.cl> wrote: >> Hello all, >> >> I was wondering what actually the inspector does in the following case: >> >> When you explore (or inspect) the expression: Class environment >> you get all classes in the system dictionary. If you navigate inside a class, for example AColorSelectorMorph, you can see all its properties and one of them is environment, if you go inside it, you get again all classes in the system dictionary. So, you can repeat this infinitely (or until you get run out of memory, I guess) >> >> Is it the behavior of a lazy inspector? If true, why I cannot inspect a mutually-recursive class definition, like this: >> >> Object subclass: #Foo >> instanceVariableNames: 'bar' >> classVariableNames: '' >> poolDictionaries: '' >> category: '' >> >> Foo>>initialize >> bar:= Bar new >> >> Object subclass: #Bar >> instanceVariableNames: 'foo' >> classVariableNames: '' >> poolDictionaries: '' >> category: '' >> >> Foo>>initialize >> bar:= Foo new >> >> here should be foo := Foo new. >> >> Anyway, you should be able to browse these classes without problems. >> The problems is in instance creation. For example, if you evaluate: Foo new. > > Thanks Mariano. May be my question was not well explained. Of course if I evaluate: Foo new, I get into a infinite loop. 1st question, when I'm inspecting, I'm evaluating? > > hehehehe yes :) > Just open a Transcript and inspect: Transcript show: 'welooo' > and you will see 'welooo' in the transcript ;) > > What you actually inspect, is the result of the expression. > > > > In the case that I mention above (Class enviroment) I got all classes in the system and each of them has an environment, that is all classes, and so on. Here, we have a infinite recursion. > > I understand now. > > So, how the inspector get a lazy visualization of the it? > > > I have no idea. But in this case, #environment is a method, not an instVar as your case. > Maybe in the case of the methods, they are only displayed when clicking on it (they just execute the compiledMethod). But this is just a guess. > You should check the class Inspector and NewInspector. > > Cheers > > Mariano > > Greetings > > > > _______________________________________________ > 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

Oct. 18, 2010

Re: [Pharo-project] Speeding up Pharo 1.1

by Nicolas Cellier

2010/10/17 Levente Uzonyi <leves(a)elte.hu>: > On Sat, 16 Oct 2010, Bart Veenstra wrote: > >> Hi list, >> >> I have been working with Pharo for almost a month now, and I suspect >> that the performance is degrading fast. UI tasks takes several seconds >> to react to my keyboard. > > That kind of sluggishness is probably related to finalization/gc. Please > send us the result of the following expression: > > (WeakArray classPool at: #FinalizationDependents) > Â Â Â Â select: [ :each | each notNil ] > Â Â Â Â thenCollect: [ :each | each class -> each size ] > While updating pharo 1.2, after an EndOfCentralDirectory error, I got a very unresponsive image... ((WeakArray classPool at: #FinalizationDependents) as: Array) select: [ :each | each notNil ] thenCollect: [ :each | each class -> each size] -> {(WeakIdentityKeyDictionary->22370). (WeakRegistry->0). (WeakRegistry->0). (WeakRegistry->0). (WeakRegistry->2)} I tried to inspect it 5 minutes ago, but hey, answer in another email... Ah, OK, cmd+shift+. just worked. I had to interrupt #finalizationProcess itself finally... Oh inspect is sorting the keys... unusable. So what's in the array ? Things like (ScriptLoader>>#update12125 "a CompiledMethod(0)")->a MCMethodDefinition(ScriptLoader>>update12125) (PragmaCollector>>#release "a CompiledMethod(964689920)")->a MCMethodDefinition(PragmaCollector>>release) (Float>>#arcSin "a CompiledMethod(358088704)")->a MCMethodDefinition(Float>>arcSin) I don't understand yet, but I begin to gather clues why updating pharo goes so badly... Nicolas

Oct. 18, 2010

Re: [Pharo-project] call for scripting idea

by Tudor Girba

How about getting the scripts from the Hudson integration (builder) of Lukas and translating them into Smalltalk? Cheers, Doru On 18 Oct 2010, at 21:52, stephane ducasse wrote: > Hi > > we would like to exercise a bit our scripting engine :) so if you have ideas of scripts that we should be able to write let us know. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

Oct. 18, 2010

Re: [Pharo-project] Some questions about pharo

by StÃ©phane Ducasse

in this case we should focus on the next item and provide two images one for the debugging scenario and one for normal running of script. Stef On Oct 18, 2010, at 9:58 PM, Pavel Krivanek wrote: > On Mon, Oct 18, 2010 at 9:05 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >> The Windows vm displays a system tray icon that allows the image to leave the headless state. It has been quite useful, but there should be (hopefully is) a way to prevent that. > > I think that someone asked on squeak-dev some time ago and Andreas > told that it is not possible with the standard VM. > > -- Pavel > > >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] >> Sent: Monday, October 18, 2010 2:09 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Some questions about pharo >> >> See <http://book.seaside.st/book/advanced/deployment/maintaining/vnc>. >> >> Cheers, >> Lukas >> >> 2010/10/18 Adrien BARREAU <abarreau.dev(a)live.fr>: >>> Hello =) >>> >>> I have a few questions: >>> >>> - If I run a headless Pharo, is it possible to display the graphical >>> interface after? (for example, if something raises an exception, I want to >>> open the GUI and use the debugger) >>> >>> - I wanna run Pharo as a deamon; how can I interact with it after i launched >>> it? (for example, if I want to give it a piece of code to execute). >>> >>> Adrien. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> 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

Oct. 18, 2010

Re: [Pharo-project] [squeak-dev] SharedQueue does scale (was: Re: SharedQueue doesn't scale)

by Levente Uzonyi

On Mon, 18 Oct 2010, StÃ©phane Ducasse wrote: >> >> This benchmark is the real concurrent stress test. 100 processes are adding 10,000 elements to the queue while another 100 are reading from it. It clearly shows that Igor's queues are an order of magnitude faster. Also 200 concurrent processes cause much less slowdown compared to the sequential tests for them. >> >> So, even though SharedQueue is now faster than SharedQueue2, both will have to go IMHO. :) > > Hi Levente > > Naively why? Did you see the benchmarks? > and replace by what? By Igor's new collections. Though the name should be kept for compatibility reasons. Levente > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 18, 2010

Re: [Pharo-project] Stack should be reimplemented with Array

by StÃ©phane Ducasse

Eliot > There was a post on this list back in August complaining about Stack inheriting from LinkedList. There was some discussion, but apparently no resolution, as Stack still inherits from LinkedList in the Pharo 1.2 Core Image I just downloaded. Rather than reimplementing it to forward to a contained LinkedList, I think it should use an Array internally like OrderedCollection does. An Array-based implementation of Stack would be faster than one based on LinkedList due to the basic stack operations (push, pop and top) being able to rely more on primitives. This assumes that you know roughly how a big a stack you need; if you don't, reallocating the array and copying its contents over and over again will cost you, but this is an exceptional case;-- most stacks are small and when they aren't, the programmer usually has enough information to select a reasonable stack size. > > *No*. Stack and OrderedCollection differ *usefully*. Adding an item to a Stack is always O(1). Adding an item to an OrderedCollection is O(N) because when the array overflows a new one must be allocated and the old objects copied to the new. Why not apply your speedups to OrderedCollection, or is that not possible? If not possible, then come up with a new name and add that. Please /don't/ change Stack. I would really like not having Stack inheriting from LinkedList (I hate subclassing). Now from a VM point of view is there a constraint that Stack as to be a subclass of LList? > > > Enclosed is a fileout of an Array-based Stack implementation. It trounces the LinkedList-based implementation easily, but more interestingly, it performs better than an OrderedCollection when used like a stack: > > Pushing is roughly ~30% faster: > r1 :=[100000 timesRepeat: [ > s := Stack new. > 10 timesRepeat: [s push: #foo]]] timeToRun. > r2 := [100000 timesRepeat: [ > oc := OrderedCollection new. > 10 timesRepeat: [oc addLast: #foo]]] timeToRun. > 100 - ((r1 / r2) asFloat * 100). > > as is pushing + popping: > r3 := [100000 timesRepeat: [ > s := Stack new. > 10 timesRepeat: [s push: #foo]. > 10 timesRepeat: [s pop]]] timeToRun. > r4 := [100000 timesRepeat: [ > oc := OrderedCollection new. > 10 timesRepeat: [oc addLast: #foo]. > 10 timesRepeat: [oc removeLast]]] timeToRun. > 100 - ((r3 / r4) asFloat * 100). > _______________________________________________ > 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

Oct. 18, 2010

Re: [Pharo-project] Some questions about pharo

by Pavel Krivanek

On Mon, Oct 18, 2010 at 9:05 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > The Windows vm displays a system tray icon that allows the image to leave the headless state. Â It has been quite useful, but there should be (hopefully is) a way to prevent that. I think that someone asked on squeak-dev some time ago and Andreas told that it is not possible with the standard VM. -- Pavel > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] > Sent: Monday, October 18, 2010 2:09 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Some questions about pharo > > See <http://book.seaside.st/book/advanced/deployment/maintaining/vnc>. > > Cheers, > Lukas > > 2010/10/18 Adrien BARREAU <abarreau.dev(a)live.fr>: >> Hello =) >> >> I have a few questions: >> >> - If I run a headless Pharo, is it possible to display the graphical >> interface after? (for example, if something raises an exception, I want to >> open the GUI and use the debugger) >> >> - I wanna run Pharo as a deamon; how can I interact with it after i launched >> it? (for example, if I want to give it a piece of code to execute). >> >> Adrien. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > 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 >

Oct. 18, 2010

[Pharo-project] call for scripting idea

by stephane ducasse

Hi we would like to exercise a bit our scripting engine :) so if you have ideas of scripts that we should be able to write let us know. Stef

Oct. 18, 2010

Re: [Pharo-project] A Lazy Inspector?

by Mariano Martinez Peck

2010/10/18 Oscar E A Callau <oalvarez(a)dcc.uchile.cl> > > On Oct 18, 2010, at 14:44 , Mariano Martinez Peck wrote: > > On Mon, Oct 18, 2010 at 4:40 AM, Oscar E A Callau <oalvarez(a)dcc.uchile.cl> > wrote: > >> Hello all, >> >> I was wondering what actually the inspector does in the following case: >> >> When you explore (or inspect) the expression: Class environment >> you get all classes in the system dictionary. If you navigate inside a >> class, for example AColorSelectorMorph, you can see all its properties and >> one of them is environment, if you go inside it, you get again all classes >> in the system dictionary. So, you can repeat this infinitely (or until you >> get run out of memory, I guess) >> >> Is it the behavior of a lazy inspector? If true, why I cannot inspect a >> mutually-recursive class definition, like this: >> >> Object subclass: #Foo >> instanceVariableNames: 'bar' >> classVariableNames: '' >> poolDictionaries: '' >> category: '' >> >> Foo>>initialize >> bar:= Bar new >> >> Object subclass: #Bar >> instanceVariableNames: 'foo' >> classVariableNames: '' >> poolDictionaries: '' >> category: '' >> >> Foo>>initialize >> bar:= Foo new >> > > here should be foo := Foo new. > > Anyway, you should be able to browse these classes without problems. > The problems is in instance creation. For example, if you evaluate: Foo > new. > > > Thanks Mariano. May be my question was not well explained. Of course if I > evaluate: Foo new, I get into a infinite loop. 1st question, when I'm > inspecting, I'm evaluating? > hehehehe yes :) Just open a Transcript and inspect: Transcript show: 'welooo' and you will see 'welooo' in the transcript ;) What you actually inspect, is the result of the expression. > In the case that I mention above (Class enviroment) I got all classes in > the system and each of them has an environment, that is all classes, and so > on. Here, we have a infinite recursion. > I understand now. > So, how the inspector get a lazy visualization of the it? > > I have no idea. But in this case, #environment is a method, not an instVar as your case. Maybe in the case of the methods, they are only displayed when clicking on it (they just execute the compiledMethod). But this is just a guess. You should check the class Inspector and NewInspector. Cheers Mariano > Greetings > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 18, 2010