Usually when you want to archive more performance ex. in mongrel or
thin( i dont know how the webrick, ebb,… works) in powerfull machines
ppl start new process in other ports and direct the requests for each
process.
Why do this? Isnt better start new threads in only one process?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Diego B. wrote:
| Usually when you want to archive more performance ex. in mongrel or
| thin( i dont know how the webrick, ebb,… works) in powerfull machines
| ppl start new process in other ports and direct the requests for each
| process.
| Why do this? Isnt better start new threads in only one process?
‘Multi-core’. You can shift multiple processes around on multiple CPUs.
And then there’s the nastiness of thread-blocking. In such a case, a
process possibly has to wait for a thread to complete. That is not
really desirable, if you have more than one concurrent request.
Also, if one process gets into a deadlock, it doesn’t take your whole
web-server with it.
Phillip G.
Twitter: twitter.com/cynicalryan
Blog: http://justarubyist.blogspot.com
~ I have plenty of common sense, I just choose to ignore it.
~ — Calvin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkgyEAAACgkQbtAgaoJTgL+nSgCdEIqvMP/bvvbjxxTv6e3KrowQ
eKMAn09QLjtKJBIBBSIpLAUMLmhgW7VL
=TSSg
-----END PGP SIGNATURE-----