4 ms·
There's no inherent reason why multiprocess would have a significant impact on energy, it just adds a relatively small amount of extra context switching and mar
by _wmd 11y ago
There's no inherent reason why multiprocess would have a significant impact on energy, it just adds a relatively small amount of extra context switching and marshalling to what is already a huge pile of the same (your desktop OS). When the system is idle, or a page is rendered, the difference shouldn't be measurable.
- deleted 11y ago[deleted]
- nitrogen 11y agoHypothetically, 50 processes all running separate unsynchronized wakeup timers and event loops could bring the processor out of sleep 50x more often than a single process.
- frik 11y agoI assume all graphics data is sent from the tab sub-processes to the main process (Chrome and similar in IE9-11). Multiprocess is different in Firefox, to get full multiprocess (per tab) we maybe have to wait a bit longer, for a Servo based browser. Launching processes is a bit expensive especially on WinNT series (up to Win10), but ultimately it's the way to go ("sandbox" = sub-processes with minimum permissions) - even Servo with its Rust language use it as certain parts like the JavaScript engine are still C/C++ based (come from Firefox/gecko) for the near future and can crash.