On 2006-09-20 19:10, Bill Moran wrote: > In response to Birger Blixt > The problem is that depending on your data and usage of the database, > YMMV. Optimizations that work for one person might not benefit > another. > > For example: adding indexes _usually_ speeds query performance, but > it also _usually_ slows insert/update performance, because every change > to the table has to update all the indexes. > > If you're interested in very fast backups and rarely do restores, it > might be a bad idea to add any indexes to improve looks in the database > if it slows down the updates. On the other hand, if getting at your > data quickly is important, it might be worth slower backups to be > able to search the data quickly. > > People who have lots of jobs vs. folks with only a few jobs. A few > large files vs. lots of small files. One big server vs. many servers. > > Each of these scenarios will distribute the data differently in the > database, and cause different optimizations to be worthwhile. > Additionally, the hardware on which the DB runs makes a difference: > fast disk and low RAM vs. lots of RAM and slow disks. > > I recommend trying out indexes. It's pretty simple to remove them > if they don't work out. But don't forget to test backup performance > as well, since adding an index may speed dbcheck, but hurt your > backup speed. >
Yes, correct , but in my case as an Ex: legato admin, that got my backup servers and tape silo outsourced :-( , I use bacula for test environment , and things we will keep in house, like firewall logs and our network install server for all current linux dists. One day we maybe have a "business case" for a new backup system, and at that time I can present a ready to use bacula system I hope. So, it must be optimal for a demo restore :-), nobody cares what it's doing at night, except our network police. The day we crash a raid volume , it's easy to add any index while we fix the hardware, so it can be optimal for backup, and optimal for restore on request. I use disk spool, so the database inserts will come in clusters, so it's easy to identify problems in case of to many indexes. At home is a different story, where I only have a slow DLT 4000 drive, and it's make no big difference how fast mysql is. Look at the result after my dbcheck :-) http://www.norsborg.net/bacula/report.php?default=1&server=BackupCatalog /birger ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
