Share on Facebook0Share on Google+0Share on LinkedIn0Share on Reddit2Tweet about this on Twitter0

In the modern IT world, almost every tech guy, no matter a systems administrator or an engineer, wants his environment to show the best results that can be squeezed out of the hardware. In this article, I want you to take a look at the StarWind support of an iSER technology which stands for the iSCSI Extensions for RDMA.

There’s not much of a change in the overall system configuration. iSER is utilizing the common iSCSI protocol by using the RDMA transport service that can be used on some network adapters with hardware offload capability. This means that iSER can supply higher bandwidth, intended for large transfers of block storage data.

RDMA feature

iSER nowise replaces the current iSCSI protocol but increases the performance of the environment and provides important iSCSI features such as high availability and security of the network connection. It transfers data directly from the application memory to the network adapter, avoiding few additional network layers and decreasing system’s CPU utilization.

There are few simple steps to enable iSER in the StarWind environment. Of course, for using this feature, you will need an environment with StarWind Virtual SAN configured and the hardware that supports RDMA feature. In order to turn on iSER technology in StarWind, you need to click on a server which is connected to the StarWind Management Console, go to Configuration tab, and choose Network menu.

StarWind Network properties

In the Network menu, you can see a list of IP addresses that are currently used for StarWind Virtual SAN. You can add new IP addresses or modify the current ones. To enable iSER technology, you need to check the Enable iSER for the Interface box in the opened Network Interface window.

Enabling iSER technology

Now, the actual performance numbers come. As was said at the very beginning of this article, iSER uses common iSCSI protocol but with a little difference. So, I think that the best scenario will be to compare the performance and system load metrics between the iSCSI protocol and the iSER technology.

For the performance test, I used host-to-host configuration. The first server consists of Microsoft Windows Server 2016 with StarWind Virtual SAN installed. It will be used as a target server for another host which is VMware ESXi 6.5. Both servers have Mellanox ConnectX-4 network adapters with an iSER protocol support.

iSER performance test configuration

On the ESXi server, there are two datastores connected, with one of them being the iSCSI datastore and another – the iSER datastore. The performance test is being run from the Windows VMs, that are located on these datastores.

StarWind Virtual SAN eliminates any need for physical shared storage just by mirroring internal flash and storage resources between hypervisor servers. Furthermore, the solution can be run on the off-the-shelf hardware. Such design allows StarWind Virtual SAN to not only achieve high performance and efficient hardware utilization but also reduce operational and capital expenses.
Learn more about ➡ StarWind Virtual SAN.

Server configuration:

  • Intel Xeon E5-2660
  • 128GB RAM
  • Mellanox ConnectX-4 100GbE NICs, direct connect
  • 2x Intel DC S3100 SSDs in RAID0
  • VMware ESXi, 6.5.0, 6765664
  • Windows Server 2016
  • StarWind Virtual SAN, build 11660

Generally speaking, iSER is based on shortening the TCP/IP stack of a transfer protocol. Thus, it allows the system increasing the overall IOPS numbers as well as decreasing the latency and lowering the CPU utilization.

You can see from the graph below, that using the iSER technology instead of a common iSCSI protocol gives us better performance on the most usable patterns. Especially it can be seen on sequential 64k write and read blocks, the difference here is more than two times higher with iSER.

StarWind iSER vs iSCSI IOPS

 

The overall latency gets decreased by avoiding the TCP/IP stack and bypassing the target’s CPU. In some cases, the iSCSI protocol has a bit lower utilization. This can be explained by having much higher IOPS on small random blocks. However, in the mixed patterns, iSER uses fewer CPU resources than iSCSI.

As a conclusion from all the information mentioned above, the iSER data transfer extension for iSCSI RDMA gives us a number of benefits that are useful for building a virtualized environment. Using the iSER technology makes the configuration faster in terms of IOPS, additionally unloading the system’s CPU utilization and decreasing the latency between the servers. If your system has the possibility of using RDMA, StarWind iSER support will definitely come in handy.

However, I’ll try to cover more interesting tests with the iSER technology in the future, so stay tuned!

Related materials:

Views All Time
1
Views Today
7
Appreciate how useful this article was to you?
No Ratings Yet
Loading...
Back to blog
The following two tabs change content below.
Alex Khorolets
Alex Khorolets
Starting as a hobbyist in virtualization and storage sphere, Alex works as a technical support engineer at StarWind. Has a broad knowledge in networking, storage technologies, and clustering.

Filed under:
Software by Alex Khorolets