> Hi! Hi > We just came accross DBMAIL because we require for a new application of > ours an IMAP server that scales well. > We were already thinking along simmilar lines regarding an IMAP frontend > to mysql, but as our requirements are outside the "25000" account range > given in the readme I am not sure, if the solution would scale to our > requirements! > > So I am asking for input for if a setup like this would be feasable: > * Users: 200000 > * Messages/User: 80 > * Avereage Message size: 100k > * 1 new Mail/second > > So that would sum up to 1.6TB of storage of storage-requirements. > Currently we are planing for 3x overcommit, so this would reduce to > 0.5TB of actual storage.
Nice, fair old size. > That is why I am a little bit sceptic if the "one" table > storage-solution that dbmail provides (dbmail_messageblks) would scale > that well. > Another thing that I am a little bit scared, is that 0.5TB in one table > might become a bottleneck in the end... > The other thing ist that for performance reasons we definitely would > like to split the data over several disks... You can use mysql merge tables instead of innodb or myisam, this will allow you to split the data in to as many physical tables as you wish (works out as a single virtual table). http://dev.mysql.com/doc/mysql/en/merge-storage-engine.html Not sure how you'd span that over multiple disks thought, be interested to find out - quick google search and I found this ' Split databases and tables over different disks. In MySQL you can use symbolic links for this.' Cunning! http://dev.mysql.com/tech-resources/presentations/presentation-oscon2000-200 00719/ Have a look through the list archives, there are people already doing this. http://mailman.fastxs.net/pipermail/dbmail/ > Any ideas, if such a setup is feasable with dbmail and if it would scale? > > Input would be greately appreciated... HTH Simon
