On 2013-10-02 11:01, Reindl Harald wrote:
Am 02.10.2013 11:05, schrieb Thomas Raschbacher:
I just noticed that my daily dbmail-util run was taking like forever
to run. At first I was confused as to why but
then I remembered somethign on the git log (I am using
abac5b58c94f270e534320ff264054bc79530b78 at the moment for
testing) and found this:
http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1&id=a40b41d783fde2ff2304dd8bb61a70448be26810
Now I have a postgres process for this connection:
(from top)
11069 postgres 20 0 114m 79m 76m R 97,8 0,5 1821:00
postgres: dbmail dbmail ::1(47006) DELETE
this seems to be terribly inefficient (transaction start, DELETE,
transaction commit - rinse&repeat).
It might be because I got quite a lot of mails in there which are
migrated from an old db, but the time this takes
is still rather long imho.
I don't know about all the DB backends, but wouldn'T it be a lot more
efficient to do this in one query (with
subselect) or a - very short stored procedure (which should be easy to
maintain on all the platforms).
as it stands now I can't really run this daily anymore :(
the problem is that you may have *a very large* amount because this
was not cleared
in the past from 3.0 until the commit
a40b41d783fde2ff2304dd8bb61a70448be26810
this should be much more relaxed if it runs daily
my homeserver hammered on the RAID10 for some minutes, but only at the
first run
I don't have a problem with some Minutes
but look at my top output .. 1821 Minutes!! that's over 30 Hours !
and yes i worded that badly I mean until it is done once I can't run
this daily
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
