Shaun Adams wrote:
1. The ibdata1 file size is 10GB. Does that sound right? Should this file
be this big?
That sounds right. Innodb seems to incur large space overheads. but with
the cost of diskspace nowadays...
2. Once a week, I have to perform HUGE insert imports into the database.
What is the recommended procedure for doing this? Clearing out memory with
a FLUSH before I start the import, setting innodb_flush_log_at_trx_commit to
0... any other suggestions
Yeah the flush log at trx_commit is good. remember that if the machine
crashes you gotta retry the last second of txns before the crash. Also,
turn of autocommit and surround your query(s) with SET AUTCOMMIT=0 and
COMMIT; If the db crashes while you're doing a lot of inserts, the
rollback can take FOREVER. and i do mean forever. check the mysql manual
on how to avoid this.
In general try not to do mass inserts at any given time. Perhaps build a
queue and stream rows into the database as you need them.
3. Could you all recommend any tips you have used to increase performance
using INNODB (from a system admin's
look into replication if you need a lot of performance. otherwise just a
lot of memory (if you have more than 4GB you'll need a 64bit OS). scsi
(or otherwise high rotational) drives tend to work faster. If the
database is 99% reads and you need all the performance you can get, i
think MyISAM is a better option.
4. Finally, could you take a look at my settings below as well as the system
variables and recommend any changes.
Looks alright. i think the biggest thing is having a large innodb log file.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
