|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Benjamin Schmidt (schmidi2
directbox.com)
Date: Mon Nov 26 2007 - 12:44:27 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Rabbitson wrote:
> Benjamin Schmidt wrote:
>> Hey
>>
>> We use dbmail (older version) for archieving eMails (1G or more per
>> day). It's horror with dbmail I just wanna say that ! ! You will have
>> a very huge innodb file. mysqldump will stop working when this file
>> reaches a size of ~40 GB (if I remember correctly). Also the db schema
>> is very innefficient for searching. A search frontend you have to
>> develop anyway.
>>
>
> Using DBMail 2.2.7 here as a local message store. 15GB of email, 26GB of
> data files on an optimized MySQL (innodb_file_per_table=1). No issues
> with performance on any operation including searches. I can run
> mysqldump without a problem but it is largely useless as a backup -
> loading the data back in will take too long. LVM snapshots + binlogs is
> my backup strategy.
>
> My 2c
>
>
>
Hey Peter
Year, the database schema of version 2.2.x looks significant better.
Still we use version 2.0.x because rewriting doesn't make sense in my
opinion. Using a database only and really only for indexing I would
prefer because I had really stress with a database of more than 100 GB
size. Going to fail would mean going to loose my apprenticeship.
Rather many little (up to ~50 MB or so) files than one huge file ;)
LVM snapshots: Sounds promising. I am gonna use it in our environment.
innodb_file_per_table=1: This option too, didn't know about it but
sounds good.
Thank you for giving me some very useful tips.
Best regards,
Benjamin Schmidt
- application/x-pkcs7-signature attachment: S/MIME Cryptographic Signature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]