未加星标

Profiling and Optimizing V8 Memory Consumption

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二04 | 时间 2016 | 作者 红领巾 ] 0人收藏点击收藏

For the last few months, the V8 team has focused on reducing the memory consumed by the V8 engine, including work on the newIgnition interpreter, and improvements to V8’s parser and compilers. A key enabler of this process was profiling V8 memory usage using specific tools against a benchmark, as explained by V8 engineers Ulan Degenbaev, Michael Lippautz, Hannes Payer, and Toon Verwaest.

To reduce V8’s memory footprint, the V8 team monitored its two heaps the C++ and the javascript heap using a new feature in Chrome 54: the --trace-gc-object-stats flag, that makes V8 dump memory-related statistics to the console. That output is then visualized using a custom tool, the V8 heap visualizer , which shows a timeline-based view for both heaps and provides a detailed breakdown of the memory usage of certain data types. Another tool that the V8 team used for this kind of analysis is Chrome’s Trace Event Profiling Tool , which is available under about:tracing .

What memory analysis showed is that one of the main factors determining the JavaScript heap size is the balance between latency and memory consumption of the garbage collector. You can improve latency by reserving more memory to the heap to avoid frequent GC invocations. This may however be a problem for low-memory devices and lead to crashes or suspended apps. To strike a better balance between latency and memory consumption, the V8 team has introduced a new memory reduction mode that favors more frequent collections and reduces memory fragmentation through more aggressive compactions. The new memory reduction more brought an overall 50% reduction in V8 heap size on a reference benchmark. Another optimization that has been introduced consisted in reducing the V8 heap page size from 1M to 512K, benefiting both overall memory usage and memory fragmentation.

The V8 team could also reduce the C++ heap size by improving background parsing, which allows V8 to parse script while the page is still being loaded. In fact, as the memory visualization tool showed, the background parser would keep a heap zone alive long after the code had been compiled, instead of releasing it immediately. Additionally, the V8 parser is now using a more aggressive strategy to pack fields in the abstract syntax tree nodes it generates, whereas the standard C++ packing was relied upon previously. Benchmarking showed a peak zone memory reduction of about 40% on average.

All improvements described above will be available in Chrome 55, expected to become available in December.

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

主题: ChromeC++JavaScriptJava
分页:12
转载请注明
本文标题:Profiling and Optimizing V8 Memory Consumption
本站链接:http://www.codesec.net/view/480691.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(30)