May 24, 2012

Post: Testing Samsung SSD SATA 256GB 830 - not all SSD created equal

… pricing point our customers are looking for cheaper alternatives. SATA SSD is an options. There is many products based on MLC… use sysbench fileio, 16KiB block size (to match workload from InnoDB, as this is primary usage for me), and recently I… IO mode. There are two reasons for that. First, MySQL/InnoDB uses async writes, so this will emulate database load, and…

Post: Testing STEC SSD MACH16 200GB SLC

… use sysbench fileio, 16KiB block size (to match workload from InnoDB, as this is primary usage for me), and recently I… IO mode. There are two reasons for that. First, MySQL/InnoDB uses async writes, so this will emulate database load, and… 4 STEC MACH16 cards. If you are interested more in SSD and MySQL questions – I will be giving a webinary “MySQL…

Comment: FlashCache: first experiments

You said “* InnoDB files layout: ibdata1 and ib_logfile* are placed on separate RAID partition ( not on FlashCache or SSD)” Why did you exclude ibdata1 from flashcache ? I think flashcache is good place to store ibdata(innodb system tablespace…

Post: ext4 vs xfs on SSD

… getting a lot of question if this is good for SSD, or something else (i.e. xfs) should be used. Traditionally… one more point to consider. Starting the MySQL 5.1 + InnoDB-plugin and later MySQL 5.5 (or equally Percona Server… asked, namely: “If MySQL 5.5 uses async IO, is innodb_write_io_threads still important?”, and it seems it is…

Comment: Percona Server vs MySQL on Intel 320 SSD

Patrick, There are two factors: 1. Speed of recovery is much better in MySQL/Percona Server 5.5 2. Having on SSD makes it also much faster. So having big log files is practical under these conditions. It still may be long, but that that painful as in old InnoDB.

Comment: ext4 vs xfs on SSD

Useful results for when we move to SSDs.. Were sync_binlog=1 and innodb_flush_at_trx_commit=1 ?

Post: SSD, XFS, LVM, fsync, write cache, barrier and lost transactions

InnoDB on SSD outperforms RAID 10, but recently I faced issue which can make previous results inconsistent. In short words using Intel SSD X25-E card with enabled write-cache (which is default and most performance mode) does not warranty storing all InnoDB… on SSD and running very primitive test with INSERT INTO fs VALUES(0) into auto-increment field into InnoDB table. InnoDB parameters are innodb

Post: Fast storage: 8 SSD Intel X-25M 80GB benchmarks

…: – For sequential reads you can get pretty decent results from SSD (230MB/sec on 4+ threads) – Cards connected in hardware raid… InnoDB transactional logs on rotation based drives instead of SSD in my InnoDB on FusionIO benchmarks). So in summary I can say With SSD… single FusionIO card, however there is important point that with SSD you may “hot”remove and insert cards, while for FusionIO…

Post: Heikki Tuuri answers to Innodb questions, Part II

… algorithm. I’m also wondering if you would recommend using SSD for this purpose, and how much performance gain there might… rules can be established. I have assigned Inaam as the InnoDB scalability engineer. We do not have much resources for scalability… not showed up in “show innodb status”. select * from table where id=5 show innodb status: Hash table size 10624987, used…

Post: RAID vs SSD vs FusionIO

… all three devices (RAID was on board; Intel X25-E SSD connected to HighPoint controller, FusionIO card) on our working horse… on all devices. For tests I used MySQL 5.4/InnoDB, and all other parameters are the same from previous posts… (see my post http://www.mysqlperformanceblog.com/2009/03/02/ssd-xfs-lvm-fsync-write-cache-barrier-and-lost-transactions/). While…