Comments on: Putting your storage to the test – Part 2 NFS on Iomega IX4-200D http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/ Your P.I. on virtualization Tue, 07 Feb 2012 11:19:00 +0000 hourly 1 By: Gabes Virtual WorldPerformance test of Iomega StorCenter PX4-300R - Gabes Virtual World http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-1680 Gabes Virtual WorldPerformance test of Iomega StorCenter PX4-300R - Gabes Virtual World Tue, 27 Sep 2011 09:07:19 +0000 http://www.gabesvirtualworld.com/?p=949#comment-1680 [...] two blogposts: Putting your storage to the test – Part 1 iSCSI on Iomega StorCenter IX4-200D and part 2. Recently Iomega sent me their new StorCenter PX4-300R for testing purpose and I was happy to run [...] [...] two blogposts: Putting your storage to the test – Part 1 iSCSI on Iomega StorCenter IX4-200D and part 2. Recently Iomega sent me their new StorCenter PX4-300R for testing purpose and I was happy to run [...]

]]> By: Welcome to vSphere-land! » Storage Links http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-1527 Welcome to vSphere-land! » Storage Links Fri, 08 Jul 2011 15:10:29 +0000 http://www.gabesvirtualworld.com/?p=949#comment-1527 [...] mutual NFS customers using VMware (Virtual Geek) Using NAS for virtual machines (Storage Magazine) Putting your storage to the test Part 2 NFS on Iomega IX4-200D (Gabe’s Virtual World) Best Practices for Running vSphere on NFS Storage (VMware) [...] [...] mutual NFS customers using VMware (Virtual Geek) Using NAS for virtual machines (Storage Magazine) Putting your storage to the test Part 2 NFS on Iomega IX4-200D (Gabe’s Virtual World) Best Practices for Running vSphere on NFS Storage (VMware) [...]

]]> By: techstarts http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-713 techstarts Sun, 07 Feb 2010 19:06:05 +0000 http://www.gabesvirtualworld.com/?p=949#comment-713 Thanks for your valuable comments and explaining my doubts. It really means a lot to me. I will be soon making recommendation to my internal team based on my findings. I give the credit to you for this....thanks once again Thanks for your valuable comments and explaining my doubts. It really means a lot to me. I will be soon making recommendation to my internal team based on my findings. I give the credit to you for this….thanks once again

]]> By: techstarts http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-634 techstarts Sun, 07 Feb 2010 12:06:05 +0000 http://www.gabesvirtualworld.com/?p=949#comment-634 Thanks for your valuable comments and explaining my doubts. It really means a lot to me. I will be soon making recommendation to my internal team based on my findings. I give the credit to you for this....thanks once again Thanks for your valuable comments and explaining my doubts. It really means a lot to me. I will be soon making recommendation to my internal team based on my findings. I give the credit to you for this….thanks once again

]]> By: Gabrie van Zanten http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-712 Gabrie van Zanten Fri, 05 Feb 2010 01:55:49 +0000 http://www.gabesvirtualworld.com/?p=949#comment-712 Hi<br><br>I wasn't sure how to work with the test connection rate either. The manual says:<br><br>"The Test Connection Rate control specifies how often the selected worker(s) open and close their network connection. The default is off, meaning that the connection is opened at the beginning of the test and is not closed until the end of the test. If you turn this control on, you can specify a number of transactions to perform between opening and closing. (A transaction is an I/O request and the corresponding reply, if any; see the Reply field in the Edit Access Specification dialog for more information).<br><br>If Test Connection Rate is on, the worker opens its network connection at the beginning of the test. When the specified number of transactions has been performed, the connection is closed, and is re-opened again just before the next I/O. The number of transactions can be zero, in which case the worker just opens and closes the connection repeatedly.<br><br>Each open + transactions + close sequence is called a connection. The time from the initiation of the open to the completion of the corresponding close is recorded for each connection, and the maximum and average connection time and the average connections per second are reported."<br><br>I did notice that changing this, does have an influence on the test. But since the test used in the VMware communities thread used the value of 500, I decided to use the same number.<br><br>2. The disk size doesn't matter that much. Just make sure the test file is more than the amount of RAM for the VM to rule out caching. So I used a 1GB RAM VM, 4 GB test file on a 50GB vmdk.<br><br>Gabrie Hi

I wasn't sure how to work with the test connection rate either. The manual says:

“The Test Connection Rate control specifies how often the selected worker(s) open and close their network connection. The default is off, meaning that the connection is opened at the beginning of the test and is not closed until the end of the test. If you turn this control on, you can specify a number of transactions to perform between opening and closing. (A transaction is an I/O request and the corresponding reply, if any; see the Reply field in the Edit Access Specification dialog for more information).

If Test Connection Rate is on, the worker opens its network connection at the beginning of the test. When the specified number of transactions has been performed, the connection is closed, and is re-opened again just before the next I/O. The number of transactions can be zero, in which case the worker just opens and closes the connection repeatedly.

Each open + transactions + close sequence is called a connection. The time from the initiation of the open to the completion of the corresponding close is recorded for each connection, and the maximum and average connection time and the average connections per second are reported.”

I did notice that changing this, does have an influence on the test. But since the test used in the VMware communities thread used the value of 500, I decided to use the same number.

2. The disk size doesn't matter that much. Just make sure the test file is more than the amount of RAM for the VM to rule out caching. So I used a 1GB RAM VM, 4 GB test file on a 50GB vmdk.

Gabrie

]]> By: Gabrie van Zanten http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-633 Gabrie van Zanten Thu, 04 Feb 2010 18:55:49 +0000 http://www.gabesvirtualworld.com/?p=949#comment-633 Hi<br><br>I wasn't sure how to work with the test connection rate either. The manual says:<br><br>"The Test Connection Rate control specifies how often the selected worker(s) open and close their network connection. The default is off, meaning that the connection is opened at the beginning of the test and is not closed until the end of the test. If you turn this control on, you can specify a number of transactions to perform between opening and closing. (A transaction is an I/O request and the corresponding reply, if any; see the Reply field in the Edit Access Specification dialog for more information).<br><br>If Test Connection Rate is on, the worker opens its network connection at the beginning of the test. When the specified number of transactions has been performed, the connection is closed, and is re-opened again just before the next I/O. The number of transactions can be zero, in which case the worker just opens and closes the connection repeatedly.<br><br>Each open + transactions + close sequence is called a connection. The time from the initiation of the open to the completion of the corresponding close is recorded for each connection, and the maximum and average connection time and the average connections per second are reported."<br><br>I did notice that changing this, does have an influence on the test. But since the test used in the VMware communities thread used the value of 500, I decided to use the same number.<br><br>2. The disk size doesn't matter that much. Just make sure the test file is more than the amount of RAM for the VM to rule out caching. So I used a 1GB RAM VM, 4 GB test file on a 50GB vmdk.<br><br>Gabrie Hi

I wasn't sure how to work with the test connection rate either. The manual says:

“The Test Connection Rate control specifies how often the selected worker(s) open and close their network connection. The default is off, meaning that the connection is opened at the beginning of the test and is not closed until the end of the test. If you turn this control on, you can specify a number of transactions to perform between opening and closing. (A transaction is an I/O request and the corresponding reply, if any; see the Reply field in the Edit Access Specification dialog for more information).

If Test Connection Rate is on, the worker opens its network connection at the beginning of the test. When the specified number of transactions has been performed, the connection is closed, and is re-opened again just before the next I/O. The number of transactions can be zero, in which case the worker just opens and closes the connection repeatedly.

Each open + transactions + close sequence is called a connection. The time from the initiation of the open to the completion of the corresponding close is recorded for each connection, and the maximum and average connection time and the average connections per second are reported.”

I did notice that changing this, does have an influence on the test. But since the test used in the VMware communities thread used the value of 500, I decided to use the same number.

2. The disk size doesn't matter that much. Just make sure the test file is more than the amount of RAM for the VM to rule out caching. So I used a 1GB RAM VM, 4 GB test file on a 50GB vmdk.

Gabrie

]]> By: techstarts http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-711 techstarts Wed, 03 Feb 2010 16:09:44 +0000 http://www.gabesvirtualworld.com/?p=949#comment-711 Thanks, it was very helpful post as far as I'm concern. I'm currently doing performance testing and using above information, I was able to test I/O characteristic in my lab. Though on physical box.<br><br>I have few question, I would be grateful if you can answer them.<br><br>1. What is the purpose of test connection Rate ? you have kept it 500<br>2. What should be the disk size? I'm using 32GB Ram server, and 60GB disk size. you have kept it 4GB<br><br>Thanks once again Thanks, it was very helpful post as far as I'm concern. I'm currently doing performance testing and using above information, I was able to test I/O characteristic in my lab. Though on physical box.

I have few question, I would be grateful if you can answer them.

1. What is the purpose of test connection Rate ? you have kept it 500
2. What should be the disk size? I'm using 32GB Ram server, and 60GB disk size. you have kept it 4GB

Thanks once again

]]> By: techstarts http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-632 techstarts Wed, 03 Feb 2010 09:09:44 +0000 http://www.gabesvirtualworld.com/?p=949#comment-632 Thanks, it was very helpful post as far as I'm concern. I'm currently doing performance testing and using above information, I was able to test I/O characteristic in my lab. Though on physical box.<br><br>I have few question, I would be grateful if you can answer them.<br><br>1. What is the purpose of test connection Rate ? you have kept it 500<br>2. What should be the disk size? I'm using 32GB Ram server, and 60GB disk size. you have kept it 4GB<br><br>Thanks once again Thanks, it was very helpful post as far as I'm concern. I'm currently doing performance testing and using above information, I was able to test I/O characteristic in my lab. Though on physical box.

I have few question, I would be grateful if you can answer them.

1. What is the purpose of test connection Rate ? you have kept it 500
2. What should be the disk size? I'm using 32GB Ram server, and 60GB disk size. you have kept it 4GB

Thanks once again

]]> By: jonowings http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-710 jonowings Mon, 11 Jan 2010 19:26:26 +0000 http://www.gabesvirtualworld.com/?p=949#comment-710 Does anyone know if the IX4 runs NFS as a base file system and iSCSI is layered on top? Could explain the performance differences. Does anyone know if the IX4 runs NFS as a base file system and iSCSI is layered on top? Could explain the performance differences.

]]> By: Ondrej http://www.gabesvirtualworld.com/putting-your-storage-to-the-test-%e2%80%93-part-2-nfs-on-iomega-ix4-200d/#comment-709 Ondrej Mon, 11 Jan 2010 13:51:23 +0000 http://www.gabesvirtualworld.com/?p=949#comment-709 I want to ask a question - where in my enviroment should I set 64K block size? On VMware server, storage, VM partition? I want to ask a question – where in my enviroment should I set 64K block size? On VMware server, storage, VM partition?

]]>