Jake Anderson wrote: > Would it be possible to create a query that we end users could run over > our databases to find out about this?
Alas, no. Currently, messages are chopped into 512k blocks. Nothing you can derive from that, short of doing some serious disk IO like full reconstruction. Such operations would be nice finger excercises in case we need to prepare migration scripts for this mime-chunking operation, but non-trivial no matter what. > mysql has a built in MD5 function, I don't really know how the DB in > DBMail really works or I'd have a go myself. > > Something along these lines though perhaps? > > create temporary table externalfilesavings > select count(*) as numfiles,md5(foo) as md5_out,len(foo) as filesize > from sometable > where is_a_msg_attachment = true > group by md5_out,filesize, order by md5_out desc; > > select sum(filesize * numfiles) as Current_On_Disk_Size,sum(filesize) as > Modified_File_size_Size from sometable; > > > > Its probably not worth it for "small" messages but where its over say > 200kb it would probably start to pay off. > Actually that would be another interesting thing to find out too, what > the spread of message sizes are. > Its really a tuning thing so some real world numbers might be in order. > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ 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
