You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great idea about comparing the both CLI in an automated way!
Would be great to see multiple runs or network proxy to remove network effects on the test results.
I tried it on one of the large ones
bestander-mbp:npm-vs-yarn bestander$ ./yarn.sh yo [email protected]:yeoman/yo.git | grep CACHE
58 s CACHE: cold, NODE_MODULES: empty, LOCKFILE: no
26 s CACHE: cold, NODE_MODULES: empty, LOCKFILE: yes
25 s CACHE: cold, NODE_MODULES: installed, LOCKFILE: no
19 s CACHE: cold, NODE_MODULES: installed, LOCKFILE: yes
21 s CACHE: warm, NODE_MODULES: empty, LOCKFILE: no
24 s CACHE: warm, NODE_MODULES: empty, LOCKFILE: yes
15 s CACHE: warm, NODE_MODULES: installed, LOCKFILE: no
9 s CACHE: warm, NODE_MODULES: installed, LOCKFILE: yes
9s sounded too much for a warm + installed + lockfile
So I ran this test manually
bestander-mbp:temp bestander$ git clone [email protected]:yeoman/yo.git
bestander-mbp:temp bestander$ cd yo/
bestander-mbp:yo bestander$ yarn install
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
[4/4] 📃 Building fresh packages...
✨ Done in 17.53s.
bestander-mbp:yo bestander$ time yarn install
yarn install v0.21.0-0
[1/4] 🔍 Resolving packages...
success Already up-to-date.
$ yodoctor
Yeoman Doctor
Running sanity checks on your system
✔ Global configuration file is valid
✔ NODE_PATH matches the npm root
✔ Node.js version
✔ No .bowerrc file in home directory
✔ No .yo-rc.json file in home directory
✔ npm version
Everything looks all right!
$ gulp prepublish
[09:48:00] Using gulpfile ~/work/temp/yo/gulpfile.js
[09:48:00] Starting 'nsp'...
[09:48:00] (+) No known vulnerabilities found
[09:48:00] Finished 'nsp' after 446 ms
[09:48:00] Starting 'prepublish'...
[09:48:00] Finished 'prepublish' after 17 μs
✨ Done in 2.82s.
real 0m3.118s
user 0m2.201s
sys 0m0.466s
I think something is off with the script.
The text was updated successfully, but these errors were encountered:
Hey I'm sorry about only getting back to you now :(
The tool actually runs every day. This way if the same version is live multiple days we actually get average results. The averaged data is in the google docs (See "data_average" row I) how many times this has run.
I am going to check why the warm, cached, installed is reporting it so slow :(
Great idea about comparing the both CLI in an automated way!
Would be great to see multiple runs or network proxy to remove network effects on the test results.
I tried it on one of the large ones
9s sounded too much for a warm + installed + lockfile
So I ran this test manually
I think something is off with the script.
The text was updated successfully, but these errors were encountered: