Re: ANNOUNCE: qmail now works with the diet libc
Thus spake Mark ([EMAIL PROTECTED]): Er, what's the chance of have a ps which compares qmail-popd, qmail-smtp and qmail-remote then? Kinda relevant doncha think? You are right. This is a diet libc pop3: USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND leitner 3232 0.4 0.05648 3 T15:30 0:00 /var/qmail/bin/qmail-pop3d Maildir root 3229 0.0 0.06848 3 T15:29 0:00 tcpserver 0 pop3 /var/qmail/bin/qmail-popup felix.convergence.de /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir root 3231 0.1 0.02020 3 T15:29 0:00 /var/qmail/bin/qmail-popup felix.convergence.de /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir This is after I logged in and retrieved one message from a Maildir of 151. And this is a diet libc smtpd (without openssl and STARTTLS): USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND root 3313 0.1 0.03636 3 S15:34 0:00 /var/qmail/bin/qmail-smtpd This is after I connected and dumped a test email of three lines. Compare for yourself. Felix
RE: ANNOUNCE: qmail now works with the diet libc
Just wondering if this is the complete truth. I think most of the time memory isn't a problem but CPU is, and I don't see/know if this diet libc is decreasing CPU load. More concurrency leads to more memory usage but also to more CPU susage. Of course I could be wrong here :) Greets, Franky -Original Message- From: Felix von Leitner [mailto:[EMAIL PROTECTED]] Sent: woensdag 6 juni 2001 22:55 To: [EMAIL PROTECTED] Subject: ANNOUNCE: qmail now works with the diet libc Why is this significant? Because it allows a much larger concurrency on the same hardware. More POP3 users, more concurrent local and remote deliveries, more incoming SMTP connections.
ANNOUNCE: qmail now works with the diet libc
I recently did a few updates to my diet libc (http://www.fefe.de/dietlibc/) and it can now compile and link qmail. Since the diet libc can also compile and link openssl, the STARTTLS patch also works. What's the difference, you ask? This ps listing is on a box with qmail dynamically linked against the glibc: USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND qmaill 29527 0.0 0.1 1228 224 ? S N Mar 12 0:16 splogger qmail qmailq 29543 0.0 0.0 1208 104 ? S N Mar 12 0:03 qmail-clean qmailr 29529 0.0 0.1 1216 176 ? S N Mar 12 0:00 qmail-rspawn qmails 29521 0.0 0.1 1260 172 ? S N Mar 12 0:22 qmail-send root 29528 0.0 0.0 121680 ? S N Mar 12 0:08 qmail-lspawn ./Maildir/ And this ps listing is from my home box, statically linked against the diet libc: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND qmails 103 0.0 0.064 56 ?S18:55 0:00 qmail-send qmaill 109 0.0 0.044 20 ?S18:55 0:00 splogger qmail root 110 0.0 0.036 24 ?S18:55 0:00 qmail-lspawn ./Maildir/ qmailr 111 0.0 0.036 24 ?S18:55 0:00 qmail-rspawn qmailq 112 0.0 0.024 16 ?S18:55 0:00 qmail-clean root 11747 1.0 0.056 40 ?S22:46 0:00 /usr/local/bin/tcpserver -u qmaild -g nofiles 0 smtp /var/qmail/b Please note the drastically reduced memory requirements. As you can see, the process are running for many days on the first box, so unused memory is already swapped out. Not so on the second box. Why is this significant? Because it allows a much larger concurrency on the same hardware. More POP3 users, more concurrent local and remote deliveries, more incoming SMTP connections. How to reproduce. 1. get the current diet libc from CVS, compile and install the diet wrapper program in your $PATH. 2. get qmail, extract and possibly apply your favourite patches. 3. set up conf-cc and conf-ld $ echo diet gcc -pipe -Os -fomit-frame-pointer conf-cc $ echo diet gcc -static -s conf-ld 4. make and make setup qmail as usual. That's it. Good luck! Felix
Re: ANNOUNCE: qmail now works with the diet libc
On Wed, Jun 06, 2001 at 10:54:33PM +0200, Felix von Leitner allegedly wrote: I recently did a few updates to my diet libc (http://www.fefe.de/dietlibc/) and it can now compile and link qmail. Since the diet libc can also compile and link openssl, the STARTTLS patch also works. What's the difference, you ask? This ps listing is on a box with qmail dynamically linked against the glibc: USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND qmaill 29527 0.0 0.1 1228 224 ? S N Mar 12 0:16 splogger qmail qmailq 29543 0.0 0.0 1208 104 ? S N Mar 12 0:03 qmail-clean qmailr 29529 0.0 0.1 1216 176 ? S N Mar 12 0:00 qmail-rspawn qmails 29521 0.0 0.1 1260 172 ? S N Mar 12 0:22 qmail-send root 29528 0.0 0.0 121680 ? S N Mar 12 0:08 qmail-lspawn ./Maildir/ Please note the drastically reduced memory requirements. As you can see, the process are running for many days on the first box, so unused memory is already swapped out. Not so on the second box. Why is this significant? Because it allows a much larger concurrency on the same hardware. More POP3 users, more concurrent local and remote deliveries, more incoming SMTP connections. Er, what's the chance of have a ps which compares qmail-popd, qmail-smtp and qmail-remote then? Kinda relevant doncha think? Regards.
