Charles Marcus wrote: > > There should obviously be a method for dealing with high-load > conditions, where DBMail stores the message initially without doing the > SIS work, but flags it for processing later when the load goes below a > pre-configured level.
I don't see how that's obvious. If we move to storing unique mime-parts only once, the only way to store any mime-part is by calculating the sha1 value for such a mime part. What you are proposing is a stepped insertion. That would require a full mail-spool type setup. Better leave that to the MTA: simply refuse SMTP/LMTP connections when the load is too high. >> Although as an indicator I timed an md5sum on a 2.4gb file and got about >> 48 seconds (Pentium D ~2.8ghz or so, 15krpm scsi hdd, ubuntu 6.10) so at >> 100% cpu you can MD5 about 50mb of data per second probably not worth >> the hassle of a separate run. Thats not so bad. (50mb emails would (I >> hope) be fairly rare?) Don't count on it. Once we have this setup, using dbmail as an archive server is that much more attractive. People may very well start using it to store big files, and a lot of it! Btw, MD5 is out. If I do this, SHA1 seems much better (less chance of collisions), unless something better shows up on the radar. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
