Le 18/04/2014 10:17, Jan P. Kessler a écrit :
You're right, old, historycal mailing lists exist on the X-Itools sourceforge project page.Hi,maybe you should set up an own mailing list for GreyLSE. The are a lot of coders at this list. If any of them would use this list to discuss their own topics it might become somewhat confusing here.
Does that mean, that it forks when a new request arrives? Keep in mind that process forking is very expensive. Take a look at preforking (simple, lots of examples) or multi-threaded models (more complex but even more efficient).Yes. I'm working on preforking (in fact, I've started to analyze prefork.c from Apache web server some days ago...). Threads are an option, but we choose forking for better isolation. Some people say forking and threading is basically the same in term of perfs, that's even written in some books dedicated to linux programming, some others have another opinion. The best would be to get our own experience about that: just for fun, that could be interesting to make a multi-threaded version to see how perfs are going. At this time in my testing conditions, the overall decision process regarding one recipient takes 0.7 milliseconds minimum, 1.5 milliseconds maximum on a huge database that is under heavy load performing also all ELSE operations (so not only GreyLSE). That means between 667 and 1428 requests/s. So average is 1047 requests/s. Conservative value: 900 requests/s, with only one database management child. A GreyLSE detached from the ELSE, with it's dedicated small DB, would we able to perform more requests/s. I'll probably also offer a way to configure the number of database childs...
Yes, a test lab this morning confirmed that. Thanks any way for this confirmation.Yes, the last option. It will reuse the connection:
Well, I've decided to not put links any more on a mailing list dedicated to postfix (this is in link with what you wrote in your first sentence...), and my posts here are very rare. If people want to take a look at this very young project module, they can find it by themselves on sourceforge (or by checking my very first posts to this postfix mailing list)So, where is your code? Did I miss a link?
<<attachment: hahnn.vcf>>
