Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 08 Mar 2012 22:14:22 -0500
From:      Daniel Staal <>
Subject:   Re: imap server performance benchmarks
Message-ID:  <>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
--As of March 9, 2012 12:44:55 PM +1000, Da Rock is alleged to have said:

> I'm reconsidering my current setup (postfix/courier) for imap and I was
> doing some research on performance comparisons between imap server
> setups. I stumbled on this article just just about fell of my chair
> laughing when I read the last article on future benchmarking tests to
> perform:
> Considering I have close to a hundred folders or more, and an average of
> 50,000 emails in each (yes, not good, and I am working on archiving but
> it won't help _that_ much) with nearly 200,000 in just one! I got a real
> kick out of the comment that "no sane email user would have more than
> 21,000 emails in a folder" - that would make me certifiable :D Oh, and
> that most email wouldn't be more than a GB or so... mine's edging 6GB
> already...
> So, all jokes aside, I contemplated that I would make an ideal test case
> to the extreme for benchmarking imap servers. Anyone have any suggestions
> on what to test/how? Anyone have some tools they have created for a
> similar challenge? I have my own ideas, but if anyone wants me to try
> something I'd be willing to give it a shot.

--As for the rest, it is mine.

No idea, but as someone who recently had to trim one of his mail folders 
(same setup) as it was having trouble with over 210,000 messages, I'd be 
interested in your results.  ;)

Daniel T. STaal

This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.

Want to link to this message? Use this URL: <>