|
! 4 @ 0 @ 4 !
Что-то пошло не так. Главная страница
Факт о медицине:
For example, in the process of writing an article, two browser windows (8 and 11 tabs) are open, as well as three separate windows in the form of web applications, in particular, Gmail. Simultaneously open Firefox 3 with 7 tabs. Now it's time to bring another browser component from Google to the stage - its own process manager (from the menu or via Shift-Esc), showing all running browser processes (as well as the flash process, from which you can try to conclude that Flash is one process for all, and it's interesting to see what happens when it crashes when several windows with flash movies are open). Examining the manager, we can draw one more conclusion - it turns out that different tabs in which pages of the same site (domain) are open will be displayed within the same parent process, using only new threads, which means that a crash on one page will only lead to the closing of tabs from pages of this domain. If you still want to spread open pages across independent threads, you will have to use new windows. However,
Медицинские новости:
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.
|
