Sorry, I used an inaccurate thread title for the previous message. I rephrase my thread title and question here (though the context in the previous post still applies):
How does process creation/maintenance overhead in Linux compare to that of other Unices (SVR4 / *BSD / Solaris)? Much better, much worse or roughly on the same order?
Apparently, one of NT's characteristics (at least for the kernel circa 1997) is that process overhead on it is significantly higher than that of Unix, thus use of threads is de rigueur on NT (and its descendants).
Now that threads on Linux and other *nixes are available, I'd like to use information on Linux process overhead to better judge when to use a process and when to use a thread under it (esp. when implementing a cross-platform architecture).
Also, can someone clarify the difference between the many different thread APIs/libraries available? i.e. pthreads vs. linux threads vs. FreeBSD's own threading (*) vs. whatever else is out there for *nix?
Interestingly enough, you can use the linuxthreads library under FreeBSD and that is supposed to be the recommended way to compile MySQL on this platform to get around certain inefficiencies (see "Revisiting FreeBSD vs. Linux for MySQL" http://jeremy.zawodny.com/blog/archives/000697.html ).
-- ============================================= reply-to: a n d y @ n e o t i t a n s . c o m http://www.neotitans.com Web and Software Development -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
