Calypso loading code spinner

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Calypso loading code spinner

Esteban A. Maringolo
It is happening to me very often that to access the source of a
method, or sometimes to find senders/implementors, the Calypso browser
takes a long time to load it.

By long I mean from two to five seconds, sometimes longer.

I'm running Pharo 7 within a VirtualBox VM with Ubuntu 16.04 in a
Windows 10 host.

Regards,

Pharo 7.0.3
Build information:
Pharo-7.0.3+build.164.sha.591a635c8922e5f1cff1d0b3fbf2e525b590d25f (64
Bit)


Esteban A. Maringolo

Annotation 2019-12-06 185028.png (100K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Calypso loading code spinner

Esteban A. Maringolo
Answering myself...

It seems to be related with the power management because as soon as I
plugged in my laptop the spinning effect went away (and also the whole
environment got faster).
Maybe it has to do with the guest OS power management, although I
didn't see any noticeable slowdown in other apps within the VM.

Is there any specific PM thing in the Pharo VM? Or should I look at
the VBOX/Ubuntu settings.

Regards.

Esteban A. Maringolo

On Fri, Dec 6, 2019 at 7:02 PM Esteban Maringolo <[hidden email]> wrote:

>
> It is happening to me very often that to access the source of a
> method, or sometimes to find senders/implementors, the Calypso browser
> takes a long time to load it.
>
> By long I mean from two to five seconds, sometimes longer.
>
> I'm running Pharo 7 within a VirtualBox VM with Ubuntu 16.04 in a
> Windows 10 host.
>
> Regards,
>
> Pharo 7.0.3
> Build information:
> Pharo-7.0.3+build.164.sha.591a635c8922e5f1cff1d0b3fbf2e525b590d25f (64
> Bit)
>
>
> Esteban A. Maringolo

Reply | Threaded
Open this post in threaded view
|

Re: Calypso loading code spinner

tbrunz
Hi Esteban,

This sounds like your host OS is powering down your laptop's HDD while on
battery, to save energy.  Plugging it in triggers a different rule that
selects "performance" over "energy savings" and keeps the drive up &
spinning constantly.

I would check the Win10 power management rules to verify this.  You can also
select a different power profile when on battery there, or create a new one
(such as "power savings except for the hard drive" when on battery).

-Ted




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html