1820136 - Use same value for jemalloc moz_set_max_dirty_page_modifier in JS shell as for foreground content processes

Status: RESOLVED FIXED

(Core :: JavaScript Engine, task, P1)

Description

[Jan de Mooij [:jandem]]

Olli's changes in bug 1815069 improved our browser performance a lot. We should use the same jemalloc settings for the JS shell so performance there is more similar to a foreground content process.

We could also add a testing function to the JS shell to allow changing this value, for both fuzzing and performance testing.

Comment 1

[Jan de Mooij [:jandem]]

Attachment: Bug 1820136 - Use moz_set_max_dirty_page_modifier and jemalloc_free_dirty_pages for the JS shell to match the browser. r?smaug!,pbone!,jonco!

This matches the behavior for foreground content processes since bug 1815069.

Also adds a testing function for fuzzing and performance testing.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d929730d9d23
Use moz_set_max_dirty_page_modifier and jemalloc_free_dirty_pages for the JS shell to match the browser. r=smaug,jonco

Comment 3

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/d929730d9d23