Let's control GC frequency and High water mark for Tracemonkey
2009/07/10 10:08 / Mozilla Contribution
We are going to control GC frequency / high-water-mark of Tracemonkey via about:config page as below.
We are able to limit memory consumption of Tracemonkey via "javascript.options.mem.high_water_mark" and "javascript.options.mem.gc_frequency". The option is set as 32 MB. However, we can change the value with new threshold when we run firefox on embedded devices. For example, let's consider that we run firefox on cell phone, TV, refrigerator and so on. They have various HW specifications. Thus, we need to limit memory usage of firefox. This feature focuses on limitation of Tracemonkey's memory consumption.
Chart below shows how GC execution/memory consumption are changed via trigger factor(javascript.options.mem.gc_frequency).
Next chart below shows how GC execution/memory consumption are changed via high_water_mark (javascript.options.mem.high_water_mark).
System under test
- OS : Ubuntu 9.04
- CPU : Intel(R) Pentium(R) 4 CPU 2.40GHz
- RAM : 1.5 GB
- Scenario : Run sunspider test after changing trigger factor and high water mark.
- Base Source code : Check out mozilla-central branch on 2009.07.11 (hg clone http://hg.mozilla.org/mozilla-central)
- Test Date : 2009 Jul. 17
In the chart, the high_water_mark influence the peak of memory usage from under 10 MB. Because, the normal memory usages are 14 MB and 9.8 MB in 32MB / 1600%.
If you have any questions, please leave a message to me.
You can find this feature in bugzilla
Bug 456721 - Control GC frequency/a high water mark of Tracemonkey via about:config
(https://bugzilla.mozilla.org/show_bug.cgi?id=456721)
We are able to limit memory consumption of Tracemonkey via "javascript.options.mem.high_water_mark" and "javascript.options.mem.gc_frequency". The option is set as 32 MB. However, we can change the value with new threshold when we run firefox on embedded devices. For example, let's consider that we run firefox on cell phone, TV, refrigerator and so on. They have various HW specifications. Thus, we need to limit memory usage of firefox. This feature focuses on limitation of Tracemonkey's memory consumption.
Chart below shows how GC execution/memory consumption are changed via trigger factor(javascript.options.mem.gc_frequency).
Next chart below shows how GC execution/memory consumption are changed via high_water_mark (javascript.options.mem.high_water_mark).
System under test
- OS : Ubuntu 9.04
- CPU : Intel(R) Pentium(R) 4 CPU 2.40GHz
- RAM : 1.5 GB
- Scenario : Run sunspider test after changing trigger factor and high water mark.
- Base Source code : Check out mozilla-central branch on 2009.07.11 (hg clone http://hg.mozilla.org/mozilla-central)
- Test Date : 2009 Jul. 17
In the chart, the high_water_mark influence the peak of memory usage from under 10 MB. Because, the normal memory usages are 14 MB and 9.8 MB in 32MB / 1600%.
If you have any questions, please leave a message to me.
You can find this feature in bugzilla
Bug 456721 - Control GC frequency/a high water mark of Tracemonkey via about:config
(https://bugzilla.mozilla.org/show_bug.cgi?id=456721)
Trackback URL : http://lakhos.cafe24.com/trackback/18
Leave your greetings here.