Thanks a lot for pointing me to DBMail. That is a piece of living proof
on how to design efficient mail storgare in DB.
I guess what I am wondering is just a simple question:
Say if a mail server is supporting 2000 accounts. Each account has
200M storage quota. Suppose after several years each account will have
several thousands (say 5000) emails. If we keep all the emails in one
table (using userID to distinguish), we'll have a table with 10 million
rows. If we keep the emails in seperate tables, we'll have 2000 tables
with 5000 rows for each.
Which one is better? From what I gather, probably one table is better
to manage - but will that cause performance problem? Say if this is a
web mail system, whenever a user login and access Inbox, you'll have to
load first page of emails from that 10-million-row table. Will the
performance be hurt even with proper indexing?
Received on Sun Apr 03 2005 - 17:52:45 CDT
