On Dec 11, 2007, at 3:42 PM, Carl Lowenstein wrote:
Ok, I gotta ask.. how the hell did a ~20meg mail trigger a problem
with a 2Gig heap limit? Program that poorly written?
Mail sent to 100 or more CC: recipients?
It's the subject of much speculation here, too. Reference was made,
at one point, to a bug with a subject similar to "don't keep full copy
of message in memory for most operations". My suspicion is that the
Zimbra developers saw that Java had a Mail framework, which has a
Message object, and might have said "Let's use that!". And then
decided that they should clone/copy that object when it needed to be
addressed to multiple recipients.
On disk, Zimbra uses a single message store, so, in theory, no matter
how many people get the message, there's only one copy on disk.
However, I can easily see why multiple copies would need to be
generated in memory for processing of a message, particularly if each
of the multiple recipients has a set of mail filters they want all
their mail processed by.
Ahhh, here's the specific bugs that were referenced to me:
http://bugzilla.zimbra.com/show_bug.cgi?id=19221
Bug 19221 - Do not hold whole message in memory
http://bugzilla.zimbra.com/show_bug.cgi?id=9509
Bug 9509 - Reduce server memory requirements
We're on 4.5.6 (testing upgrading to 4.5.10 this week), and 5.0 is
still a ways off, but these fixes are due in 5.0.
Running on a big, bad-ass server in 64-bit mode gets us by. :)
Gregory
--
Gregory K. Ruiz-Ade <[EMAIL PROTECTED]>
OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
