ember-cli: Slow build time for ember-cli

Hello, I got a slow build time here. Can anyone please help me take a look?

Output from BROCCOLI_VIZ=true ember s -p 4202:

Build successful - 78197ms.

Slowest Trees                                 | Total
----------------------------------------------+---------------------
broccoli-persistent-filter:Babel              | 26988ms
broccoli-persistent-filter:TemplateCompiler   | 15110ms
broccoli-persistent-filter:Babel > [Babel:... | 6507ms
broccoli-persistent-filter:Babel > [Babel:... | 3933ms

Slowest Trees (cumulative)                    | Total (avg)
----------------------------------------------+---------------------
broccoli-persistent-filter:Babel (5)          | 27246ms (5449 ms)
broccoli-persistent-filter:TemplateCom... (8) | 16628ms (2078 ms)
broccoli-persistent-filter:Babel > [Ba... (2) | 6605ms (3302 ms)
broccoli-persistent-filter:Babel > [Ba... (1) | 3933ms

Output from ember version --verbose && npm --version:

ember-cli: 2.7.0
http_parser: 2.7.0
node: 6.10.0
v8: 5.1.281.93
uv: 1.9.1
zlib: 1.2.8
ares: 1.10.1-DEV
icu: 58.2
modules: 48
openssl: 1.0.2k
os: darwin x64
npm:4.4.4

I have already read PERF_GUIDE.md and generated the tree graph.

According to the tree graph, there is a broccoli-persistent-filter: Babel that takes a lot of time(self 26988 ms). I uploaded that part of png. out

I would like to upload the whole png here, but it is too big (14mb), and github won’t allow me to upload.

Please let me know if there is any more information I can provide. Thanks

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 19 (4 by maintainers)

Most upvoted comments

The Babel 5/6 change struck me as suspicious timing-wise

Yes, I believe this is likely related. But surprising. Witha reproduction I could investigate. But the work-around of rm -rf node_modules; rm -rf yarn.lock; yarn install may be an alright bandaid for today?

stefanpenner on Jul 26, 2017

I did a rm -rf node_modules and then npm install and it cut my build time down from 2-3 min to ~31 seconds!

zurnet on Jul 26, 2017

@zurnet What worked for me was to empty node_modules and npm install everything again. Build times then went to the usual minute or two.

vlascik on Jul 26, 2017