aboutsummaryrefslogtreecommitdiff
path: root/bench/hot-module-reloading/readme.md
diff options
context:
space:
mode:
Diffstat (limited to 'bench/hot-module-reloading/readme.md')
-rw-r--r--bench/hot-module-reloading/readme.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/bench/hot-module-reloading/readme.md b/bench/hot-module-reloading/readme.md
new file mode 100644
index 000000000..539eb023c
--- /dev/null
+++ b/bench/hot-module-reloading/readme.md
@@ -0,0 +1,15 @@
+# Benchmarking hot module reloading
+
+## Methodology
+
+How do you benchmark hot module reloading? What do you call "done" and what do you call "start"?
+
+The answer is certainly not compilation time. Compilation time is one step.
+
+I think the answer should be different depending on the type of content loaded.
+
+For CSS, the answer should be "when the updated stylesheet was drawn on the screen"
+For JavaScript, the answer should be "when the rebuilt code completed execution such that any changes are applied"
+For images & assets, the answer should be "when the updated asset finished loading"
+
+The start time should be defined as "the timestamp the filesystem set as the write time". As in, the time the developer pressed save in their editor.