Hi!

I did the same measurement for Pharo 6.1. To summarize it I have those results: 

By executing: 

-=-=-=-
EpMonitor current disable.
[ Metacello new
  baseline: 'GToolkit';
  repository: 'github://feenkcom/gtoolkit/src';
  load.
] timeToRun
-=-=-=-

Pharo 6.1 64bit macOS: 6 minutes
Pharo 7.0 64bit macOS: 8 minutes

With EpMonitor current enabled it is: 

Pharo 6.1 64bit macOS: 7 minutes
Pharo 7.0 64bit macOS: 15 minutes


Cheers,
Juraj

On Oct 2, 2018, at 23:31, Juraj Kubelka via Pharo-dev <pharo-dev@lists.pharo.org> wrote:


From: Juraj Kubelka <juraj.kubelka@icloud.com>
Subject: Re: [Pharo-dev] Slowness when loading code in Pharo 7?
Date: October 2, 2018 at 23:31:59 GMT-3
To: Pharo Development List <pharo-dev@lists.pharo.org>


Hi Martin,

By disabling EpMonitor, the slowdown disappears.

EpMonitor current disable.
[ Metacello new
  baseline: 'GToolkit';
  repository: 'github://feenkcom/gtoolkit/src';
  load.
] timeToRun "0:00:08:03.504���


Cheers,
Juraj

On Oct 2, 2018, at 18:14, Martin Dias <tinchodias@gmail.com> wrote:

Hi Andrei. You can evaluate "EpMonitor current disable" before loading
to compare times.
El mar., 2 de oct. de 2018 a la(s) 11:18, Andrei Chis
(chisvasileandrei@gmail.com) escribi��:

Hi,

Are there any know slowdowns when loading code in Pharo 7? Usually on my machine (Mac - HighSierra) loading GToolkit in a Pharo 6.1 images takes around 9 minutes. In the latest Pharo 7 it takes 20 minutes. On two other newer laptops running Mac results are similar (15 minutes on Pharo 7 64it, and 7 minutes on Pharo 6.1 64bit).

We have the impression that most of the times, the regression happens because of reading sources file. And the sources files are read because of checking Epicea method changes. We have not done a deep research on it, just whenever we do CMD+. it stops in that stage.

Cheers,
Andrei