-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, Aug 15, 2008 at 03:37:53PM -0300, Sebastien Tandel wrote:
[...]
[fork is fast]
OK, it measures the fork instruction. But fork is using a copy-on-write mechanism ... It means that *none* of the parent's memory pages are copied. Each page is simply *shared* by *all* the child /until/ a modification is made to it.Therefore this test obviously does not take into account time taken when modifying data. And I strongly suspect that dovecot is not only doing read-only access to memory when running. :-/
Yep, but what can you do after pre-forking and before the request comes in?
Thus I'd expect pre-forking not to save us much which can't be saved by prudent programming (save mentioned exception of > thousands of connects per second).
We are now deeply in specula-land, I guess ;-)
Regards
- -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIplsTBcgs9XrR2kYRAlnWAJ9N4no7nCvu9f/psXBpFJdBhYEwMgCZAWfe EPXLY1QCdx999EXv4q/tbf8= =7bCz -----END PGP SIGNATURE-----