Hi -
I've recently installed Pharo 1.4 & 2.0 on a laptop I upgraded to Ubuntu 13.04 and using both Eliot's vm for Pharo 1.4 and the pharovm from the Ubuntu PPA. The UI is incredibly slow with it sometimes taking 1 second to switch windows when they are clicked or > 8 seconds to find the senders/implementors of a method. Is there something I can check to see what the problem may be? cat /proc/cpuinfo shows that the CPU is running at the high frequency. Thanks Paul |
Paul,
On 05 Jun 2013, at 23:52, Paul DeBruicker <[hidden email]> wrote: > Hi - > > I've recently installed Pharo 1.4 & 2.0 on a laptop I upgraded to Ubuntu > 13.04 and using both Eliot's vm for Pharo 1.4 and the pharovm from the > Ubuntu PPA. The UI is incredibly slow with it sometimes taking 1 second > to switch windows when they are clicked or > 8 seconds to find the > senders/implementors of a method. Is there something I can check to see > what the problem may be? > > cat /proc/cpuinfo shows that the CPU is running at the high frequency. > > Thanks > > Paul It is probably best to open an issue, I couldn't find one. Can you find out if it is VM, image or OS related, by elimination ? There were/are other problems with Ubuntu 13.04, due to an upgraded libc if I am not mistaken. Sorry that I can't be of any more assistance. Sven |
In reply to this post by Paul DeBruicker
On Wed, Jun 5, 2013 at 11:52 PM, Paul DeBruicker <[hidden email]> wrote:
> I've recently installed Pharo 1.4 & 2.0 on a laptop I upgraded to Ubuntu > 13.04 and using both Eliot's vm for Pharo 1.4 and the pharovm from the > Ubuntu PPA. The UI is incredibly slow with it sometimes taking 1 second > to switch windows when they are clicked or > 8 seconds to find the > senders/implementors of a method. Is there something I can check to see > what the problem may be? > > cat /proc/cpuinfo shows that the CPU is running at the high frequency. I'm also using 13.04 (but mine is 32bits). I can *not* reproduce your problem with the VM on the PPA. Just to be sure, I sent new versions of the packages to the https://launchpad.net/~pharo/+archive/stable/ PPA this morning. They will be ready in a few hours. Is there anything special with your image? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill |
Hi Damien,
Because of the attached Message Tally outputs I don't think the problem is specific to changes I've made to an image. I also don't think that there is much differnece between Eliots vm or the pharo ppa vm. The Message Tally outputs are from profiling the UI while finding the senders of #setUp using various VM & image combinations. On squeak finding the senders of #setUp seems instantaneous. On Pharo it takes multiple seconds to find and display the senders. It may be my expectations are different than they should be. Is the result from the pharo ppa vm + pharo 2 image similar to what you're seeing on the 32bit Ubuntu? Thanks for looking into this. For what its worth I'm using a 5 yr old Dell D630 laptop with an 3GB of ram and a 120 GB SSD. I've also attached the output from /proc/cpuinfo Please let me know if there are other things I should check. Paul On 06/06/2013 12:31 AM, Damien Cassou wrote: > On Wed, Jun 5, 2013 at 11:52 PM, Paul DeBruicker <[hidden email]> wrote: >> I've recently installed Pharo 1.4 & 2.0 on a laptop I upgraded to Ubuntu >> 13.04 and using both Eliot's vm for Pharo 1.4 and the pharovm from the >> Ubuntu PPA. The UI is incredibly slow with it sometimes taking 1 second >> to switch windows when they are clicked or > 8 seconds to find the >> senders/implementors of a method. Is there something I can check to see >> what the problem may be? >> >> cat /proc/cpuinfo shows that the CPU is running at the high frequency. > > > I'm also using 13.04 (but mine is 32bits). I can *not* reproduce your > problem with the VM on the PPA. Just to be sure, I sent new versions > of the packages to the https://launchpad.net/~pharo/+archive/stable/ > PPA this morning. They will be ready in a few hours. > > Is there anything special with your image? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > cpuinfo (1K) Download Attachment pharo-ppa-vm-pharo-1.4 (14K) Download Attachment squeak-4.4-all-in-one (6K) Download Attachment eliots-vm-my-1.4-image (15K) Download Attachment pharo-ppa-vm-pharo-2 (21K) Download Attachment pharo-ppa-vm-my-1.4-image (18K) Download Attachment |
> Hi Damien, > > > Because of the attached Message Tally outputs I don't think the problem > is specific to changes I've made to an image. I also don't think that > there is much differnece between Eliots vm or the pharo ppa vm. The > Message Tally outputs are from profiling the UI while finding the > senders of #setUp using various VM & image combinations. On squeak > finding the senders of #setUp seems instantaneous. On Pharo it takes > multiple seconds to find and display the senders. ouch! So may be we have a regression in an iteration. > It may be my expectations are different than they should be. No I do not see why sender would take ages. > Is the result from the pharo ppa vm + pharo 2 image similar to what > you're seeing on the 32bit Ubuntu? > > Thanks for looking into this. For what its worth I'm using a 5 yr old > Dell D630 laptop with an 3GB of ram and a 120 GB SSD. I've also > attached the output from /proc/cpuinfo > > Please let me know if there are other things I should check. > > Paul > > > On 06/06/2013 12:31 AM, Damien Cassou wrote: >> On Wed, Jun 5, 2013 at 11:52 PM, Paul DeBruicker <[hidden email]> wrote: >>> I've recently installed Pharo 1.4 & 2.0 on a laptop I upgraded to Ubuntu >>> 13.04 and using both Eliot's vm for Pharo 1.4 and the pharovm from the >>> Ubuntu PPA. The UI is incredibly slow with it sometimes taking 1 second >>> to switch windows when they are clicked or > 8 seconds to find the >>> senders/implementors of a method. Is there something I can check to see >>> what the problem may be? >>> >>> cat /proc/cpuinfo shows that the CPU is running at the high frequency. >> >> >> I'm also using 13.04 (but mine is 32bits). I can *not* reproduce your >> problem with the VM on the PPA. Just to be sure, I sent new versions >> of the packages to the https://launchpad.net/~pharo/+archive/stable/ >> PPA this morning. They will be ready in a few hours. >> >> Is there anything special with your image? >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > > <cpuinfo.txt><pharo-ppa-vm-pharo-1.4><squeak-4.4-all-in-one><eliots-vm-my-1.4-image><pharo-ppa-vm-pharo-2.txt><pharo-ppa-vm-my-1.4-image> |
In reply to this post by Paul DeBruicker
On Jun 6, 2013, at 5:12 PM, Paul DeBruicker <[hidden email]> wrote: > Hi Damien, > > > Because of the attached Message Tally outputs I don't think the problem > is specific to changes I've made to an image. I also don't think that > there is much differnece between Eliots vm or the pharo ppa vm. The > Message Tally outputs are from profiling the UI while finding the > senders of #setUp using various VM & image combinations. On squeak > finding the senders of #setUp seems instantaneous. On Pharo it takes > multiple seconds to find and display the senders. > This is really strange… here even doing "senders of" for all the >6000 senders of ifTrue: is quite fast for 2.0 and even faster in 3.0. So I really wonder what the problem is... Marcus |
could we get the image so that we can try?
Stef On Jun 7, 2013, at 8:27 AM, Marcus Denker <[hidden email]> wrote: > > On Jun 6, 2013, at 5:12 PM, Paul DeBruicker <[hidden email]> wrote: > >> Hi Damien, >> >> >> Because of the attached Message Tally outputs I don't think the problem >> is specific to changes I've made to an image. I also don't think that >> there is much differnece between Eliots vm or the pharo ppa vm. The >> Message Tally outputs are from profiling the UI while finding the >> senders of #setUp using various VM & image combinations. On squeak >> finding the senders of #setUp seems instantaneous. On Pharo it takes >> multiple seconds to find and display the senders. >> > > This is really strange… here even doing "senders of" for all the >6000 senders > of ifTrue: is quite fast for 2.0 and even faster in 3.0. > > So I really wonder what the problem is... > > Marcus |
In reply to this post by Marcus Denker-4
On 2013-06-07, at 08:27, Marcus Denker <[hidden email]> wrote: > > On Jun 6, 2013, at 5:12 PM, Paul DeBruicker <[hidden email]> wrote: > >> Hi Damien, >> >> >> Because of the attached Message Tally outputs I don't think the problem >> is specific to changes I've made to an image. I also don't think that >> there is much differnece between Eliots vm or the pharo ppa vm. The >> Message Tally outputs are from profiling the UI while finding the >> senders of #setUp using various VM & image combinations. On squeak >> finding the senders of #setUp seems instantaneous. On Pharo it takes >> multiple seconds to find and display the senders. >> > > This is really strange… here even doing "senders of" for all the >6000 senders > of ifTrue: is quite fast for 2.0 and even faster in 3.0. > > So I really wonder what the problem is... the provided profiling evidence shows the same. Pharo 1.4 / 2.0 on cog doesn't show any anomalies :/. But I must say that I had an image as well that behaved similarly recently... |
In reply to this post by Stéphane Ducasse
I thought the profiles showed it wasn't specific to my image but happened on both Pharo 1.4 & 2 using a cog vm on Ubuntu 13.04 64 bit.
On Jun 7, 2013, at 12:44 AM, Stéphane Ducasse <[hidden email]> wrote: > could we get the image so that we can try? > > Stef > > On Jun 7, 2013, at 8:27 AM, Marcus Denker <[hidden email]> wrote: > >> >> On Jun 6, 2013, at 5:12 PM, Paul DeBruicker <[hidden email]> wrote: >> >>> Hi Damien, >>> >>> >>> Because of the attached Message Tally outputs I don't think the problem >>> is specific to changes I've made to an image. I also don't think that >>> there is much differnece between Eliots vm or the pharo ppa vm. The >>> Message Tally outputs are from profiling the UI while finding the >>> senders of #setUp using various VM & image combinations. On squeak >>> finding the senders of #setUp seems instantaneous. On Pharo it takes >>> multiple seconds to find and display the senders. >>> >> >> This is really strange… here even doing "senders of" for all the >6000 senders >> of ifTrue: is quite fast for 2.0 and even faster in 3.0. >> >> So I really wonder what the problem is... >> >> Marcus > > |
In reply to this post by Marcus Denker-4
For the attached profile I downloaded a new pharo 20606 image and ran
the search for senders of #ifTrue: twice. It shows that it took 17 seconds on Ubuntu 13.04 64bit. How long does it take on your machine? On 06/06/2013 11:27 PM, Marcus Denker wrote: > > On Jun 6, 2013, at 5:12 PM, Paul DeBruicker <[hidden email]> wrote: > >> Hi Damien, >> >> >> Because of the attached Message Tally outputs I don't think the problem >> is specific to changes I've made to an image. I also don't think that >> there is much differnece between Eliots vm or the pharo ppa vm. The >> Message Tally outputs are from profiling the UI while finding the >> senders of #setUp using various VM & image combinations. On squeak >> finding the senders of #setUp seems instantaneous. On Pharo it takes >> multiple seconds to find and display the senders. >> > > This is really strange… here even doing "senders of" for all the >6000 senders > of ifTrue: is quite fast for 2.0 and even faster in 3.0. > > So I really wonder what the problem is... > > Marcus > pharo-vm-pharo-20606-ifTrue-twice (26K) Download Attachment |
On 07 Jun 2013, at 15:44, Paul DeBruicker <[hidden email]> wrote: > For the attached profile I downloaded a new pharo 20606 image and ran > the search for senders of #ifTrue: twice. It shows that it took 17 > seconds on Ubuntu 13.04 64bit. How long does it take on your machine? [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> 258 "milliseconds" I feel for you, Paul, this is really annoying... > On 06/06/2013 11:27 PM, Marcus Denker wrote: >> >> On Jun 6, 2013, at 5:12 PM, Paul DeBruicker <[hidden email]> wrote: >> >>> Hi Damien, >>> >>> >>> Because of the attached Message Tally outputs I don't think the problem >>> is specific to changes I've made to an image. I also don't think that >>> there is much differnece between Eliots vm or the pharo ppa vm. The >>> Message Tally outputs are from profiling the UI while finding the >>> senders of #setUp using various VM & image combinations. On squeak >>> finding the senders of #setUp seems instantaneous. On Pharo it takes >>> multiple seconds to find and display the senders. >>> >> >> This is really strange… here even doing "senders of" for all the >6000 senders >> of ifTrue: is quite fast for 2.0 and even faster in 3.0. >> >> So I really wonder what the problem is... >> >> Marcus >> > > <pharo-vm-pharo-20606-ifTrue-twice.txt> |
In reply to this post by Paul DeBruicker
On Jun 7, 2013, at 3:45 PM, Paul DeBruicker <[hidden email]> wrote: > For the attached profile I downloaded a new pharo 20606 image and ran > the search for senders of #ifTrue: twice. It shows that it took 17 > seconds on Ubuntu 13.04 64bit. How long does it take on your machine? > [SystemNavigation new browseMessageList: (SystemNavigation new allCallsOn: #ifTrue:) name: 'Senders or Users of ', #ifTrue: autoSelect: #ifTrue: ] timeToRun ->> 743 0.7 seconds. out of that, [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun takes ca. 0.11 seconds. |
On 2013-06-07, at 16:03, Marcus Denker <[hidden email]> wrote: > > On Jun 7, 2013, at 3:45 PM, Paul DeBruicker <[hidden email]> wrote: > >> For the attached profile I downloaded a new pharo 20606 image and ran >> the search for senders of #ifTrue: twice. It shows that it took 17 >> seconds on Ubuntu 13.04 64bit. How long does it take on your machine? On my virtualbox ubuntu 13.04 [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun == 1052 :/ |
In reply to this post by Sven Van Caekenberghe-2
Le 07/06/2013 16:00, Sven Van Caekenberghe a écrit : > > On 07 Jun 2013, at 15:44, Paul DeBruicker <[hidden email]> wrote: > >> For the attached profile I downloaded a new pharo 20606 image and ran >> the search for senders of #ifTrue: twice. It shows that it took 17 >> seconds on Ubuntu 13.04 64bit. How long does it take on your machine? > > [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> 258 "milliseconds" 20606, Ubuntu 13.04 64bits, Core i3-2350M CPU @ 2.30GHz [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> [292, 330] ms Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 |
In reply to this post by Camillo Bruni-3
My laptop is:
[SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 1518 On 06/07/2013 07:07 AM, Camillo Bruni wrote: > > On 2013-06-07, at 16:03, Marcus Denker <[hidden email]> wrote: > >> >> On Jun 7, 2013, at 3:45 PM, Paul DeBruicker <[hidden email]> wrote: >> >>> For the attached profile I downloaded a new pharo 20606 image and ran >>> the search for senders of #ifTrue: twice. It shows that it took 17 >>> seconds on Ubuntu 13.04 64bit. How long does it take on your machine? > > On my virtualbox ubuntu 13.04 > > [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun == 1052 > > :/ > |
In reply to this post by Goubier Thierry
Sounds like I need some new hardware then?
On 06/07/2013 07:16 AM, Goubier Thierry wrote: > > > Le 07/06/2013 16:00, Sven Van Caekenberghe a écrit : >> >> On 07 Jun 2013, at 15:44, Paul DeBruicker <[hidden email]> wrote: >> >>> For the attached profile I downloaded a new pharo 20606 image and ran >>> the search for senders of #ifTrue: twice. It shows that it took 17 >>> seconds on Ubuntu 13.04 64bit. How long does it take on your machine? >> >> [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> 258 >> "milliseconds" > > 20606, Ubuntu 13.04 64bits, Core i3-2350M CPU @ 2.30GHz > [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> [292, 330] ms > > Thierry |
I'll check with some older hardware; I have something slower than yours,
but I'll have the results later tonight. Thierry Le 07/06/2013 17:04, Paul DeBruicker a écrit : > Sounds like I need some new hardware then? > > > > > On 06/07/2013 07:16 AM, Goubier Thierry wrote: >> >> >> Le 07/06/2013 16:00, Sven Van Caekenberghe a écrit : >>> >>> On 07 Jun 2013, at 15:44, Paul DeBruicker <[hidden email]> wrote: >>> >>>> For the attached profile I downloaded a new pharo 20606 image and ran >>>> the search for senders of #ifTrue: twice. It shows that it took 17 >>>> seconds on Ubuntu 13.04 64bit. How long does it take on your machine? >>> >>> [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> 258 >>> "milliseconds" >> >> 20606, Ubuntu 13.04 64bits, Core i3-2350M CPU @ 2.30GHz >> [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> [292, 330] ms >> >> Thierry > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 |
In reply to this post by Paul DeBruicker
On Jun 7, 2013, at 5:04 PM, Paul DeBruicker <[hidden email]> wrote: > My laptop is: > > [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 1518 > > (3.0): [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 117 I have a slow machine: 1.8Ghz Core i5 in a MacBook Air. It auto-overclocks to 2.8 Ghz when not using two cores. It's supposed to be not a fast system, as far as I understood. Marcus |
In reply to this post by Goubier Thierry
OK. I'm going to check on a 12.04 vm and windows xp vm on this hardware
right now. I'll report back in a bit On 06/07/2013 08:13 AM, Goubier Thierry wrote: > I'll check with some older hardware; I have something slower than yours, > but I'll have the results later tonight. > > Thierry > > Le 07/06/2013 17:04, Paul DeBruicker a écrit : >> Sounds like I need some new hardware then? >> >> >> >> >> On 06/07/2013 07:16 AM, Goubier Thierry wrote: >>> >>> >>> Le 07/06/2013 16:00, Sven Van Caekenberghe a écrit : >>>> >>>> On 07 Jun 2013, at 15:44, Paul DeBruicker <[hidden email]> wrote: >>>> >>>>> For the attached profile I downloaded a new pharo 20606 image and ran >>>>> the search for senders of #ifTrue: twice. It shows that it took 17 >>>>> seconds on Ubuntu 13.04 64bit. How long does it take on your machine? >>>> >>>> [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> 258 >>>> "milliseconds" >>> >>> 20606, Ubuntu 13.04 64bits, Core i3-2350M CPU @ 2.30GHz >>> [ SystemNavigation new allSendersOf: #ifTrue: ] timeToRun =>> [292, >>> 330] ms >>> >>> Thierry >> >> >> >> > |
In reply to this post by Marcus Denker-4
Can you try on the command line only?
curl get.pharo.org/30+vm | bash ./pharo Pharo.image eval "[SystemNavigation new allCallsOn: #ifTrue: ] timeToRun" On 2013-06-07, at 17:12, Marcus Denker <[hidden email]> wrote: > > On Jun 7, 2013, at 5:04 PM, Paul DeBruicker <[hidden email]> wrote: > >> My laptop is: >> >> [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 1518 >> >> > (3.0): > [SystemNavigation new allCallsOn: #ifTrue: ] timeToRun 117 > > I have a slow machine: 1.8Ghz Core i5 in a MacBook Air. > It auto-overclocks to 2.8 Ghz when not using two cores. > > It's supposed to be not a fast system, as far as I understood. > > Marcus > > |
Free forum by Nabble | Edit this page |