3 ms·
I don't know if I'm using anything fancy, but Firefox currently is running 20 processes on my computer. According to pstree: 3*[Isolated Web Co───28*[{Iso
by mgbmtl 4y ago
I don't know if I'm using anything fancy, but Firefox currently is running 20 processes on my computer.
According to pstree:
3*[Isolated Web Co───28*[{Isolated Web Co}]]
3*[Isolated Web Co───29*[{Isolated Web Co}]]
2*[Isolated Web Co───26*[{Isolated Web Co}]]
Isolated Web Co───27*[{Isolated Web Co}]
Privileged Cont───25*[{Privileged Cont}]
RDD Process───2*[{RDD Process}]
Socket Process───4*[{Socket Process}]
Utility Process───2*[{Utility Process}]
2*[Web Content───9*[{Web Content}]]
Web Content───10*[{Web Content}]
WebExtensions───28*[{WebExtensions}]
chrome-gnome-sh───2*[{chrome-gnome-sh}]
firefox-bin
129\*[{firefox-bin}]
- znpy 4y agoThose single processes are still mostly single threaded. Don’t get me wrong, it’s still a huge leap forward to have a single webpage running in its own process, but there’s ample room for improvement. That’s what GP is referring to.
- water8 4y agoAnd a given OS is running about 1000 threads at the same time. Unless you specifically set all your apps to very high priority / nice numbers, Your thread will still spend a lot of time waiting between context switches even if it does execute faster when it finally gets one of the few cores available
- tambourine_man 4y agoI just ran Speedometer 2.0 on Chrome on macOS: Single core: 61.1 4 cores: 73.7 Speedometer tests a bunch of ToDO MVC apps in many popular frameworks. It's very heavy on DOM manipulation, parsing, painting, etc. It's the hard to parallelize stuff and stuff that's supposed to represent real world usage. JetStream 2 is easier to multithread since it plays with Web Workers and other tricks, but still, results are depressing: Single core: 54.4 4 cores: 82