On 25 Jan 2002, David Wheeler wrote: > On Fri, 2002-01-25 at 09:08, Perrin Harkins wrote: > > <snip /> > > > It's much better to build your system, profile it, and fix the bottlenecks. > > The most effective changes are almost never simple coding changes like the > > one you showed, but rather large things like using qmail-inject instead of > > SMTP, caching a slow database query or method call, or changing your > > architecture to reduce the number of network accesses or inter-process > > communications. > > qmail-inject? I've just been using sendmail or, preferentially, > Net::SMTP. Isn't using a system call more expensive? If not, how does > qmail-inject work?
With qmail, SMTP generally uses inetd, which is slow, or daemontools, which is faster, but still slow, and more importantly, it anyway goes: perl -> SMTP -> inetd -> qmail-smtpd -> qmail-inject. So with going direct to qmail-inject, your email skips out a boat load of processing and goes direct into the queue. Of course none of this is relevant if you're not using qmail ;-) -- <!-- Matt --> <:->Get a smart net</:->
