[Dovecot] Scalability plans: Abstract out filesystem and make it someone else's problem

[Timo Sirainen]

On Aug 13, 2009, at 8:13 AM, Charles Marcus wrote:

> I'm also having trouble figuring out how using hard links (or their
> equivalent) for messages with large attachments and having only one
> instance of the attachment could cause *more* disk I/O than having
> dozens/hundred of multiple copies of the message.

The thinking is that nowadays seeks are what's killing disk I/O, so  
whenever possible just do a single large read. With single instance  
storage there would be one additional seek (if the message wasn't  
already in memory).