|
! 4 @ 0 @ 4 !
Что-то пошло не так. Главная страница
Факт о медицине:
But back to memory consumption - Google Chrome consumes 185 MB of memory in this configuration versus about 60 MB for Firefox (in terms of: 8.5 MB / page for both), but three times more virtual memory (about 350 MB versus 115). It turns out that not everything is so bad and the overhead with this architecture is not particularly large, although on computers with little memory it is unlikely to be so fast, especially if there are many applications in parallel - frequent use of the paging file can significantly slow down the work.
Медицинские новости:
JavaScript is handled by the new V8 engine , which is also open source and is fast and efficient in memory management. V8 is available in source codes for all platforms (written in C ++), and can be built as a standalone application or embedded in others (for more details , see the documentation). The main advantage of the engine is faster access to object fields (in principle, it can be implemented with just one instruction), as well as the rejection of intermediate code transformations, JavaScript is translated at the first call immediately into machine code (as I understand it, into assembler). The last trump card is the built-in garbage collector, which allows you to save memory, which is especially true for complex and large JS applications. This all sounds like a description of the ideal engine, but the war on this front is just beginning, because Firefox 3.1 should also handle JS code better, and in fact, as far as I know, the next generation Tamarin engine is not even used yet.
|
