IO Performance Tuning - Revision history

Qadmin: /* SSD Tuning */

2014-05-02T16:44:36Z

SSD Tuning

← Older revision		Revision as of 16:44, 2 May 2014
Line 56:		Line 56:

	The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone.		The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone.
	Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead. Note that the flat area in the graphs on the front-right side are set to zero because that's a section where tests were not run either due to the transfer size being larger ~~that~~ the file size or the transfer size being so small vs the file size that it would not produce additional valuable numbers. Testing was done using standard iozone parameters with an increased 2G file size (iozone -a -g 2g -b output.xls), numbers with a 8GB file size were very similar.		Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead. Note that the flat area in the graphs on the front-right side are set to zero because that's a section where tests were not run either due to the transfer size being larger than the file size or the transfer size being so small vs the file size that it would not produce additional valuable numbers. Testing was done using standard iozone parameters with an increased 2G file size (iozone -a -g 2g -b output.xls), numbers with a 8GB file size were very similar.

	[[File:qs_zfs_ssd_read.png\|800px]]		[[File:qs_zfs_ssd_read.png\|800px]]

Qadmin: /* SSD Tuning */

2014-05-02T16:42:46Z

SSD Tuning

← Older revision		Revision as of 16:42, 2 May 2014
Line 58:		Line 58:
	Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead. Note that the flat area in the graphs on the front-right side are set to zero because that's a section where tests were not run either due to the transfer size being larger that the file size or the transfer size being so small vs the file size that it would not produce additional valuable numbers. Testing was done using standard iozone parameters with an increased 2G file size (iozone -a -g 2g -b output.xls), numbers with a 8GB file size were very similar.		Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead. Note that the flat area in the graphs on the front-right side are set to zero because that's a section where tests were not run either due to the transfer size being larger that the file size or the transfer size being so small vs the file size that it would not produce additional valuable numbers. Testing was done using standard iozone parameters with an increased 2G file size (iozone -a -g 2g -b output.xls), numbers with a 8GB file size were very similar.

	[[File:qs_zfs_ssd_read.png]]		[[File:qs_zfs_ssd_read.png\|800px]]

	[[File:qs_zfs_ssd_write.png]]		[[File:qs_zfs_ssd_write.png\|800px]]

	= iSCSI Performance Tuning Overview =		= iSCSI Performance Tuning Overview =

Qadmin: /* Profile IO Scheduler */

2014-05-02T16:41:29Z

Profile IO Scheduler

← Older revision		Revision as of 16:41, 2 May 2014
Line 51:		Line 51:

	The IO scheduler represents the elevator algorithm used for [http://en.wikipedia.org/wiki/Deadline_scheduler scheduling] I/O operations. For storage applications the two best schedulers are the 'deadline' and the 'noop' scheduler. We find that deadline is best for HDDs and that the noop scheduler is best for SSDs.		The IO scheduler represents the elevator algorithm used for [http://en.wikipedia.org/wiki/Deadline_scheduler scheduling] I/O operations. For storage applications the two best schedulers are the 'deadline' and the 'noop' scheduler. We find that deadline is best for HDDs and that the noop scheduler is best for SSDs.
			The fifo_batch setting is related to the use of the 'deadline' scheduler. More information can be found [http://en.wikipedia.org/wiki/Deadline_scheduler here].


	== SSD Tuning ==		== SSD Tuning ==

Qadmin: /* Storage Pool IO Tuning Overview */

2014-05-02T16:39:53Z

Storage Pool IO Tuning Overview

@@ Line 36: / Line 36: @@
 </pre>
-The ''name'' and ''description'' fields will show up in the QuantaStor web interface so be sure to make these unique.  The nr_requests represents the IO queue size.  This is an important variable to change on the host side as well if you're connecting to your QuantaStor appliance via [http://www.monperrus.net/martin/scheduler+queue+size+and+resilience+to+heavy+IO iSCSI from a Linux based server].  In QuantaStor when you set the
+=== Profile Name & Description ===
 == SSD Tuning ==

Qadmin: /* Storage Pool IO Tuning Overview */

2014-05-02T16:23:04Z

Storage Pool IO Tuning Overview

@@ Line 22: / Line 22: @@
 scheduler=noop
 </pre>
 == SSD Tuning ==

Qadmin: /* SSD Tuning */

2014-05-02T16:16:20Z

SSD Tuning

← Older revision		Revision as of 16:16, 2 May 2014
Line 26:		Line 26:

	The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone.		The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone.
	Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead. Note that the flat area in the graphs on the front-right side are set to zero because that's a section where tests were not run either due to the transfer size being larger that the file size or the transfer size being so small vs the file size that it would not produce additional valuable numbers. Testing was done using standard iozone parameters with an increased 2G file size (iozone -a -g 2g -b output.xls).		Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead. Note that the flat area in the graphs on the front-right side are set to zero because that's a section where tests were not run either due to the transfer size being larger that the file size or the transfer size being so small vs the file size that it would not produce additional valuable numbers. Testing was done using standard iozone parameters with an increased 2G file size (iozone -a -g 2g -b output.xls), numbers with a 8GB file size were very similar.

	[[File:qs_zfs_ssd_read.png]]		[[File:qs_zfs_ssd_read.png]]

Qadmin: /* SSD Tuning */

2014-05-02T16:16:00Z

SSD Tuning

← Older revision		Revision as of 16:16, 2 May 2014
Line 25:		Line 25:
	== SSD Tuning ==		== SSD Tuning ==

	The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone. ~~(iozone -a -g 2g -b output.xls)~~		The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone.
	Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead. Note that the flat area in the graphs on the front-right side are set to zero because that's a section where tests were not run either due to the transfer size being larger that the file size or the transfer size being so small vs the file size that it would not produce additional valuable numbers.		Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead. Note that the flat area in the graphs on the front-right side are set to zero because that's a section where tests were not run either due to the transfer size being larger that the file size or the transfer size being so small vs the file size that it would not produce additional valuable numbers. Testing was done using standard iozone parameters with an increased 2G file size (iozone -a -g 2g -b output.xls).

	[[File:qs_zfs_ssd_read.png]]		[[File:qs_zfs_ssd_read.png]]

Qadmin: /* SSD Tuning */

2014-05-02T16:15:10Z

SSD Tuning

← Older revision		Revision as of 16:15, 2 May 2014
Line 26:		Line 26:

	The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone. (iozone -a -g 2g -b output.xls)		The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone. (iozone -a -g 2g -b output.xls)
	Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead.		Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead. Note that the flat area in the graphs on the front-right side are set to zero because that's a section where tests were not run either due to the transfer size being larger that the file size or the transfer size being so small vs the file size that it would not produce additional valuable numbers.

	[[File:qs_zfs_ssd_read.png]]		[[File:qs_zfs_ssd_read.png]]

Qadmin: /* SSD Tuning */

2014-05-02T16:11:30Z

SSD Tuning

← Older revision		Revision as of 16:11, 2 May 2014
Line 26:		Line 26:

	The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone. (iozone -a -g 2g -b output.xls)		The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone. (iozone -a -g 2g -b output.xls)
			Note that the Default SSD storage pool IO profile uses a small read-ahead of just 4k. This was the most important factor in the tuning for SSD drives. A 0KB read-ahead and larger read-ahead values seemed to create performance holes for small 4k and 8k block sizes which were eliminated with the 4KB read-ahead.

	[[File:qs_zfs_ssd_read.png]]		[[File:qs_zfs_ssd_read.png]]

Qadmin: /* Storage Pool IO Tuning Overview */

2014-05-02T16:08:08Z

Storage Pool IO Tuning Overview

← Older revision		Revision as of 16:08, 2 May 2014
Line 24:		Line 24:

	== SSD Tuning ==		== SSD Tuning ==
	The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA.
			The Default SSD tuning profile was produced after extensive testing with enterprise STEC 2TB SAS SSD drives connected to an LSI HBA. Here is some of the detail from the performance testing using iozone. (iozone -a -g 2g -b output.xls)

			[[File:qs_zfs_ssd_read.png]]

			[[File:qs_zfs_ssd_write.png]]

	= iSCSI Performance Tuning Overview =		= iSCSI Performance Tuning Overview =