Historically SeaMonkey is a single process multithreaded application.
With current versions the plugin container runs in a second process. The
(in progress) Firefox Electrolysis (e10s) project moves Firefox to a
multiprocess architecture. E10s is still a work in progress but if you
turn it on, the contents of all the tabs run in a single separate
process. Eventually each tab content may be a separate process.
Each process runs on a single core. I don't know if Gecko implements
it's own thread manager or uses OS threads. The OS may or may not run
separate threads on separate execution units. The CPU may or may not be
multithreaded. Intel high end CPUs are hyperthreaded. AMD Bulldozer
modules are clustered multithreading.
Thanks. When is this E10s supposed to be done?
--
"Every ruler sleeps on an anthill." --Afghani
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Chop ANT from its address if e-mailing privately.
Ant is currently not listening to any songs on this computer.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
