Firefox has improved its multi-process architecture in order to isolate more content while keeping memory use low:
Firefox 54 launched with a more advanced multi-process architecture than the one we saw implemented in Firefox 48 last year. The improved architecture raises the number of processes enabled by default from two to five, which Mozilla argues is a "just right" compromise between low memory usage on one side and performance and security on the other.
[...] Switching to a simpler extension model allows Firefox to enable multiple processes and also isolate them in sandboxes. Mozilla previously enabled only two processes, one for the UI and one for content, last year, in Firefox 48. This ensured that the browser wouldn't hang as much due to web pages affecting the performance of the browser interface. It also brought partial sandboxing by keeping the content isolated from the browser (as much as possible).
Mozilla is now taking it to the next level by implementing one process for the browser interface and four for content. Why four? The organization believes that this is the "just right" amount of processes to have for the majority of users, and also in terms of optimizing memory usage.
[...] Mozilla ran its own memory usage benchmarks, which showed significant memory usage reduction compared to Chrome:
- Windows 10 — Chrome used 1.77X memory as Firefox (64-bit), and 2.44X as Firefox (32-bit)
- macOS — Chrome used 1.36X memory as Firefox (64-bit)
- Linux — Chrome used 1.42X memory as Firefox (64-bit)
(Score: 0) by Anonymous Coward on Thursday June 15 2017, @03:08PM (2 children)
troll face
Did you ditch Intel for ECC support, or did you go with a "workstation" class machine?
(Score: 2) by Runaway1956 on Thursday June 15 2017, @03:24PM (1 child)
I simply cheated, LOL
$ inxi -F
System: Host: sabayon-pc Kernel: 4.7.0-sabayon x86_64 (64 bit) Desktop: Xfce 4.12.3
Distro: Sabayon Linux amd64 16.12
Machine: Mobo: Supermicro model: H8DM8-2 v: 1234567890 Bios: American Megatrends v: 080014 date: 10/22/2009
CPU(s): 2 Hexa core Six-Core AMD Opteron 8439 SEs (-HT-MCP-SMP-) cache: 6144 KB
clock speeds: max: 2814 MHz 1: 2814 MHz 2: 2814 MHz 3: 2814 MHz 4: 2814 MHz 5: 2814 MHz 6: 2814 MHz
7: 2814 MHz 8: 2814 MHz 9: 2814 MHz 10: 2814 MHz 11: 2814 MHz 12: 2814 MHz
Graphics: Card: NVIDIA GK208 [GeForce GT 730]
Display Server: X.Org 1.18.4 driver: nvidia Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
GLX Renderer: GeForce GT 730/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 370.28
Audio: Card-1 NVIDIA GK208 HDMI/DP Audio Controller driver: snd_hda_intel Sound: ALSA v: k4.7.0-sabayon
Card-2 Plantronics driver: USB Audio
Network: Card-1: NVIDIA MCP55 Ethernet driver: forcedeth
IF: enp0s8 state: up speed: 1000 Mbps duplex: full mac: 00:30:48:c8:16:72
Card-2: NVIDIA MCP55 Ethernet driver: forcedeth
IF: enp0s9 state: up speed: 1000 Mbps duplex: full mac: 00:30:48:c8:16:73
Drives: HDD Total Size: 8241.7GB (8.1% used) ID-1: /dev/sda model: MKNSSDCR240GB size: 240.1GB
ID-2: /dev/sdb model: HUA722020ALA330 size: 2000.4GB
ID-3: /dev/sdc model: HUA722020ALA330 size: 2000.4GB
ID-4: /dev/sdd model: HUA722020ALA330 size: 2000.4GB
ID-5: /dev/sde model: HUA722020ALA330 size: 2000.4GB
Partition: ID-1: / size: 22G used: 18G (84%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 168G used: 26G (17%) fs: ext4 dev: /dev/sda2
ID-3: swap-1 size: 33.56GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
RAID: Device-1: /dev/md127 - active raid: 5 components: online: 4/4 - sde1 sdc1 sdb1 sdd1
Sensors: System Temperatures: cpu: 56.0C mobo: 44.5C gpu: 48C
Fan Speeds (in rpm): cpu: 0 fan-1: 0 fan-3: 0 fan-4: 0 fan-5: 0 fan-6: 0 fan-7: 3229
fan-8: 3890
Info: Processes: 460 Uptime: 46 days Memory: 10260.4/24108.1MB Client: Shell (bash) inxi: 2.2.19
(Score: 0) by Anonymous Coward on Thursday June 15 2017, @03:40PM
nice. I got an old server instead of buying ECC RAM too.