consequences of using “innodb_flush_method = O_DIRECT” without having a battery backed write cache? or on a KVM guest?
Mysql 5.5.29 Innodb- 128GB Ram - 32 cores - Raid 10 SSD. Our server which is a dedicated KVM guest on a 'baremetal' is hosting our heavy read-write DB server. Everything is file-per-table. ...
I just inherited a Server that I have to rebuild for SQL Server 2012, I was wondering what would be the best disk configuration for the database engine. This is what I have: 6 x 300GB 10k: 2 x 1TB ...
I have a table with this structure: CREATE TABLE `requests` ( `userid` int(11) NOT NULL, `messageid` int(11) NOT NULL, `queueid` int(11) NOT NULL AUTO_INCREMENT, `problem_id` int(3) NOT NULL, ...
I am thinking of creating a dedicated partition on the harddisk for the mysql database data files in /var/lib/mysql , while considering those 2 points: a dedicated partition will avoid any file ...