Am 11.04.2012 17:09, schrieb Paul J Stevens:
> After testing with 100MB size message appends I came up with: > http://git.dbmail.eu/paul/dbmail/commit/?id=4b095dbcb956aa3538b21912ba34b0db088e4967 > which will improve the situation, but *not* fix it completely. > > The OOM situation is caused by excessive copying: > > - from the network to a receive buffer > - from the receive buffer to the token buffer > - from the token buffer to the append command's argument list > > and that's just from the imap network handler. After this the string in > the argument list is converted into a DbmailMessage object, which leads > to even more copying. > > Above patch will improve the CPU load significantly, but not the copying... > > Maybe we should set a configurable limit on APPEND message sizes. No use > allowing 1GB messages on APPEND if your MTA doesn't allow messages > larger than 100MB for example that would be perfect and trigger the error before the composer has finsihed and press "send" over WAN this is not so problematic (but well, i have seen people upload 300 MB files over 1 Mbit), it is growing by more and more users with faster internet (in my case at home 100/10 Mbit) over Gigabit LAN it kills the server within seconds
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
