On zondag, maa 2, 2003, at 16:18 Europe/Amsterdam, Paul J Stevens wrote:
All dbmail debian packages at debian.nfgd.net are 1.1
The only difference from stock 1.1. is the auto_create_mailbox patch
that circulated on the list awhile back, and a different path to
dbmail.conf
to conform to debian standards (/etc/dbmail/dbmail.conf)
The auto_create_mailbox could probably affect insertion speeds, but I
don't
see how that could affect pop performance.
Debian unstable's mysql server is currently at 3.23.55
ok. When are debian packages added to the main distribution?
I've just looked at the code. The main thing that is being done when a
large message is requested is the following:
query for all messageblks connected to a message
loop through the result of this query
per block, translate every line to a line + crlf
write translated block to output
so, i'm guessing that when a large message is requested, the pop jumps
the system resources because of the query result store. This is kind of
odd considering the fact that a database driver should handle such
requests without hogging the system. I'll write a new function for this
that will query per BLOCK_INTERVAL number of blocks a the time with
messages > 2 blocks. Will need you guys to test it though, i don't have
any testing facilities close by.
Best regards,
Eelco
Eelco van Beek - IC&S wrote:
what version of dbmail is being used?
Eelco
On zondag, maa 2, 2003, at 12:03 Europe/Amsterdam, Markus Welsch
wrote:
Hi,
I'm using the dbmail package found at
http://debian.nfgd.net/debian/unstable/
I've set up a unstable testing box and did a performance check
regarding
attachments. Here is the load whilst processing a 8 MB attachment:
Cpu(s): 99.3% user, 0.7% system, 0.0% nice, 0.0% idle
Mem: 254976k total, 163196k used, 91780k free, 21848k
buffers
Swap: 538168k total, 0k used, 538168k free, 100980k
cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ Command
2143 dbmail 18 0 3056 3056 792 R 98.7 1.2 1:28.79
dbmail-pop3d
The testing box has a 233 MHz CPU and is using the unstable version
of
Debian. The 99% CPU usage is messy ... but it would be okay if it
would
be just for a pretty short period. The problem is though that the
throughput to the client is very small ...
For small attachments (about 100 KB alltogether) the throughput is
okay
(takes a 2 seconds). But for the large one it is unfortunately just
too
slow in comparison with a daemon which is based on a file solution.
I did no tuning at all to mysql or the system in general. So it's a
out-of-the-box unstable version which includes all current updates.
Where's the main problem ?
dbMail-pop daemons or MySQL ?
If any information is required that is not included in here please
let
me know. I'd be glad to have this bottle neck solved since dbMail is
except this happening the software I want to use for the production
systems handling a load of about 8-10 GB mail per month.
If you have hardware suggestions for such a load (~ 500 users with a
mailbox size of about 15 MB in average) please post these also here!
Kind regards,
Markus
<mime-attachment>
_________________________
E.J.A. van Beek
ICT Manager
IC&S
T: +31 30 2322878
F: +31 30 2322305
PGP-key:
www.ic-s.nl/keys/eelco.txt
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_________________________
E.J.A. van Beek
ICT Manager
IC&S
T: +31 30 2322878
F: +31 30 2322305
PGP-key:
www.ic-s.nl/keys/eelco.txt
