MySQL 5.5使用裸设备存储
MySQL 5.5使用裸设备存储
MySQL的innodb支持把表和索引存储在裸设备中,存储的I/O等待问题一直是影响数据库性能的关键,裸设备不需要经过文件系统I/O处理,因而在性能上有一定的提升,在使用rhel中的kvm虚拟机的时候有明显的感觉,使用裸设备+virtio的性能基本与物理机没差别;在Oracle中,裸设备从11g开始就不被支持,而10g rac的ocr和votedisk还必须使用裸设备存储,Oracle推荐使用ASM来提升存储的I/O性能,ASM支持条带,冗余和在线添加删除磁盘组等等高级功能,同时有具有一定的可管理性;相比之下MySQL的裸设备就比较脆弱,或许在分布式基础上,MySQL单实例的数据量还不需要用裸设备来提升I/0性能,下面来演示下如何在MySQL上使用裸设备存储innodb存储类型的表和索引
一:创建LVM卷,并使用raw来绑定,其中raw1-raw5为oracle的asm磁盘
- [root@ www.bkjia.com ~]# lvcreate -n mydata -L 1G VolGroup00
- Volume Groups with the clustered attribute will be inaccessible.
- Logical volume "mydata" created
- [root@ www.bkjia.com ~]# lvs
- Skipping clustered volume group new_vg
- LV VG Attr LSize Origin Snap% Move Log Copy% Convert
- LogVol00 VolGroup00 -wi-ao 29.28G
- LogVol01 VolGroup00 -wi-ao 29.28G
- mydata VolGroup00 -wi-a- 1.00G
- [root@ www.bkjia.com ~]# cat /etc/sysconfig/rawdevices
- /dev/raw/raw1 /dev/sdb1
- /dev/raw/raw2 /dev/sdc1
- /dev/raw/raw3 /dev/sdd1
- /dev/raw/raw4 /dev/sde1
- /dev/raw/raw5 /dev/sdf1
- /dev/raw/raw6 /dev/VolGroup00/mydata
- [root@ www.bkjia.com ~]# service rawdevices restart
- Assigning devices:
- /dev/raw/raw1 --> /dev/sdb1
- /dev/raw/raw1: bound to major 8, minor 17
- /dev/raw/raw2 --> /dev/sdc1
- /dev/raw/raw2: bound to major 8, minor 33
- /dev/raw/raw3 --> /dev/sdd1
- /dev/raw/raw3: bound to major 8, minor 49
- /dev/raw/raw4 --> /dev/sde1
- /dev/raw/raw4: bound to major 8, minor 65
- /dev/raw/raw5 --> /dev/sdf1
- /dev/raw/raw5: bound to major 8, minor 81
- /dev/raw/raw6 --> /dev/VolGroup00/mydata
- /dev/raw/raw6: bound to major 253, minor 2
- done
- [root@ www.bkjia.com ~]# raw -qa
- /dev/raw/raw1: bound to major 8, minor 17
- /dev/raw/raw2: bound to major 8, minor 33
- /dev/raw/raw3: bound to major 8, minor 49
- /dev/raw/raw4: bound to major 8, minor 65
- /dev/raw/raw5: bound to major 8, minor 81
- /dev/raw/raw6: bound to major 253, minor 2
- [root@ www.bkjia.com ~]# chown mysql.mysql /dev/raw/raw6
|
评论暂时关闭