Bug 1405738 - Enable the JavaScript Start-up Bytecode Cache. r=mrbkap
authorNicolas B. Pierron <nicolas.b.pierron@mozilla.com>
Thu, 02 Nov 2017 16:31:45 +0000
changeset 443135 929b9943b4fc8af6af3d7553249995f51e02ac1d
parent 443134 d063578fc2699975f1bbc67a7190bf3fcc5494aa
child 443136 5b1cc7fdfa402533e760f1b4b5fdf9ae9dd9bcbe
push id1618
push userCallek@gmail.com
push dateThu, 11 Jan 2018 17:45:48 +0000
treeherdermozilla-release@882ca853e05a [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersmrbkap
bugs1405738
milestone58.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1405738 - Enable the JavaScript Start-up Bytecode Cache. r=mrbkap
modules/libpref/init/all.js
--- a/modules/libpref/init/all.js
+++ b/modules/libpref/init/all.js
@@ -204,17 +204,17 @@ pref("dom.keyboardevent.dispatch_during_
 // causes a separate compartment for each (addon, global) combination, which may
 // significantly increase the number of compartments in the system.
 pref("dom.compartment_per_addon", true);
 
 // Whether to enable the JavaScript start-up cache. This causes one of the first
 // execution to record the bytecode of the JavaScript function used, and save it
 // in the existing cache entry. On the following loads of the same script, the
 // bytecode would be loaded from the cache instead of being generated once more.
-pref("dom.script_loader.bytecode_cache.enabled", false);
+pref("dom.script_loader.bytecode_cache.enabled", true);
 
 // Ignore the heuristics of the bytecode cache, and always record on the first
 // visit. (used for testing purposes).
 
 // Choose one strategy to use to decide when the bytecode should be encoded and
 // saved. The following strategies are available right now:
 //   * -2 : (reader mode) The bytecode cache would be read, but it would never
 //          be saved.