Good work with the git head ;)

core
21

This is from meteor --release 1.3-modules-beta.8
http://pastebin.com/x3sDkmHS

Another run
http://pastebin.com/yWpxjhuj

22

Iā€™m sure that somewhere in the Internet thereā€™s an app which eats meteor profile outputs and displays nice graphics where you can compare different runs easily :wink: Just need to finā€¦ google it.

23

@dgreensp Currently meteor HEAD origin/master is the fastest ;( In both METEOR_PROFILE and wall time too.

http://pastebin.com/en1xketW

24

EDIT: need to double check this was actually 1.2.1

meteor 1.2.1
Another run. Really hard to have ā€œstableā€ numbers out of the testingā€¦
http://pastebin.com/dNeKupPQ

http://pastebin.com/FxzHbSqz

25

Meteor 1.2.2-faster-rebuilds.0
http://pastebin.com/47dmeRAE

26

@dgreensp

Some results measured from my app code. First timestamp is inserted into JavaScript file using sed before changing the files in meteor watched dir. Server reload time calculated when the js code actually runs (server startup js). Tests were run on https://ide.c9.io/ljack1/pitpa (where you can also collaborate https://docs.c9.io/docs/share-a-workspace :wink: instance which has 2.5GB memory, 10GB SSD disk, IntelĀ® XeonĀ® CPU @ 2.50GHz (8 core) with load averages from 4.00 to 20.

Analysis: Pretty hard to sum up from server side reload speed. However, itā€™s worth remembering that because of the way 1.3 handles the reload ( https://github.com/meteor/meteor/commit/5e9090c3ee86c21541a5bc8e4ec9bcde81251977 ) 1.3 feels MUCH faster when observed from the browser.

Times measured from code in application. Same code for all runs. 
All js/html files regenerated everytime (=updated timestamp). 
Directories timestamps unchanged.

All test results: No averages, just a single or two values from log 
after ramp-up of ~4 rebuilds.

meteor git d4d0753 (HEAD, origin/master, master):       15 seconds.

meteor 1.2.1                                            24 and 34 seconds.

--release 1.3-modules-beta.8                            19 and 29 seconds.

git checkout release-1.3                                24 seconds.

Meteor 1.2.2-faster-rebuilds.0                          22 seconds.

Meteor application source (js/html) generation script:

TS="%Y-%m-%dT%H:%M:%S.%3NZ"

function build { 
 STARTDATE=`date +$TS`
 
 sed -i.bak -e "s/SERVER_START_TIME/$STARTDATE/g"  pitpa.json    
 
 echo Starting meteor-kitchen $STARTDATE
 meteor-kitchen pitpa.json PITPA
# patch -p0 < login.patch
 echo $STARTDATE
}

Javascript inside application that measures time from html/js generation until the code actually executes:

console.log("Application server code running..");

var d1 = new Date("SERVER_START_TIME");
var d2 = new Date();

console.log("Server modified at "+d1 );
console.log("Server code reached at "+d2 );

var diff=d2-d1;
console.log("Server reload took "+
    Math.floor(diff / 1e3), 'seconds.'
);