Raevenlord
News Editor
- Joined
- Aug 12, 2016
- Messages
- 3,755 (1.24/day)
- Location
- Portugal
| System Name | The Ryzening |
|---|---|
| Processor | AMD Ryzen 9 5900X |
| Motherboard | MSI X570 MAG TOMAHAWK |
| Cooling | Lian Li Galahad 360mm AIO |
| Memory | 32 GB G.Skill Trident Z F4-3733 (4x 8 GB) |
| Video Card(s) | Gigabyte RTX 3070 Ti |
| Storage | Boot: Transcend MTE220S 2TB, Kintson A2000 1TB, Seagate Firewolf Pro 14 TB |
| Display(s) | Acer Nitro VG270UP (1440p 144 Hz IPS) |
| Case | Lian Li O11DX Dynamic White |
| Audio Device(s) | iFi Audio Zen DAC |
| Power Supply | Seasonic Focus+ 750 W |
| Mouse | Cooler Master Masterkeys Lite L |
| Keyboard | Cooler Master Masterkeys Lite L |
| Software | Windows 10 x64 |
The Mozilla Foundation has recently launched the latest version of their Firefox web browser. The foxiest web browser around, which lets you access all of those amazing websites (like TPU) now features increased support for multitasking through its multi-process technology. A result of the Electrolysis effort from Mozilla's part, which has spawned more than eight years of work, Firefox 54 applies the Goldilocks principle to browser design, straddling an approach between increased performance and acceptable memory usage.
As such, Firefox won't be like Chrome, where each process is responsible for a single tab and its content handling (and can therefore increase memory usage immensely, which has justified Chrome's fame as a memory hog), but will instead opt for a more streamlined approach. Open 10 different tabs with 10 sites in Chrome, and you'll have 10 different processes. Each of those processes has its own memory - with their own instance of the browser's engine. Au contraire, Firefox now creates up to 4 separate processes for web page content. This means that the first 4 tabs each use those 4 processes, and additional tabs run using threads within those processes, optimizing, as per Firefox, memory usage and performance.
This also means that up to a point (well, up to 4 tabs), Firefox will now be more stable should one of the tabs (and processes) fail, since they are virtually separated from the other tabs. However, should you have more than 4 tabs open, a failing tab could result in a cascading event for the other tabs open under that same process. Firefox is adding the option for users to increase the number of processes Firefox can start on the browser settings though, so if you have more than 8 GB of system RAM (the amount that Firefox is looking towards optimizing with this change), you can increase them at the expense of increased memory consumption.
View at TechPowerUp Main Site
As such, Firefox won't be like Chrome, where each process is responsible for a single tab and its content handling (and can therefore increase memory usage immensely, which has justified Chrome's fame as a memory hog), but will instead opt for a more streamlined approach. Open 10 different tabs with 10 sites in Chrome, and you'll have 10 different processes. Each of those processes has its own memory - with their own instance of the browser's engine. Au contraire, Firefox now creates up to 4 separate processes for web page content. This means that the first 4 tabs each use those 4 processes, and additional tabs run using threads within those processes, optimizing, as per Firefox, memory usage and performance.
This also means that up to a point (well, up to 4 tabs), Firefox will now be more stable should one of the tabs (and processes) fail, since they are virtually separated from the other tabs. However, should you have more than 4 tabs open, a failing tab could result in a cascading event for the other tabs open under that same process. Firefox is adding the option for users to increase the number of processes Firefox can start on the browser settings though, so if you have more than 8 GB of system RAM (the amount that Firefox is looking towards optimizing with this change), you can increase them at the expense of increased memory consumption.
View at TechPowerUp Main Site
Not much information of anything else either, so where is the schedule of nightlies dating back to 2004?2005? (I forget when it became a thing). FF64/WF is open source so ya lots of the code is shared. I like that they are interchangeable. WF recently stopped send telemetry back to mozilla, not like mozilla cared about that anyway, lol.
