understanding shared memory 3323

Dances With Crows the

Nope. I had my reasons, but bottom line, it's been a really interesting project.

low. memory-efficient else that

I'm not exec()ing anything after the fork, I'm just running another subroutine of the program that deals with the client and delivers the email.

column,

That's what I was hoping you'd say. Of the 16Mb, about half is taken up by Mail::Spambuttbuttin. I was wondering if I'd be better off running a separate Spambuttbuttin server and feeding the email to it from the SMTP server. But if the overhead in forking is not much greater with a larger program, then I'd just buttume leave it as part of the SMTP server. Is this reasoning correct, or am I missing something? I'm loading everything when the server starts, and that's why it's so big.

Will or lot

Actually, 0) it does work, and 1) it is maintainable (at least by me). I don't know where the bottlenecks are right now. It runs pretty fast, I'm just making sure I'm covering all the bases.

I tried this out, but I'm not sure how DProf handles the fork. I daemonize the process by forking right at the beginning, and I'm not sure if DProf is making it past the fork.

with

I'm running on a fast machine, with lots of RAM, but I do have more than 50 processes running at times. Probably not too often at this point, but 50 doesn't seem like too much. This mail server currently handles mail for about 2000 users, and naturally, it deals with a lot of spammers trying to abuse it in various ways.

to see

I really appreciate your help. Thanks a lot.

- Alex Hart