Hello

We compare same storage configuration only changing protocol iscsi vs nvme over roce

This storage only support thin devices, and i agree with you it could affect performance during unmap command, but on our side we have desactivate it to not put more pressure on backend

We use nvme over roce , storage is huawei 5510 configured with hybrid pool (ssd and nlsas of 14TB), between storage and esxi we use huawei ethernet 25Gb switchs also (two TOR), we have mellanox connectx4 as smart nic on esxi, we use sr iov to use vf on vm and two nic configured on vm side each with ...

feedback on my side iscsi vs nvme on my particular case i see 4% increase on bandwidth for nvme with 16k (the one that give me better result) against iscsi configure to 256k increasing to more than 16k with nvme initiator is counterproductive from what i see but also an increase of 10% of cpu usage ...

ok thx

i already tested 4k 8k and 16k , i see large improvement against default value with 16k so you're right i need to dig on this

i'm evaluating nvme initiator against iscsi. On my case i have esxi using mellanox with sr iov , vm use VF to have direct mellanox access configuration using iscsi use large block as my application did large io (lets say near 128k on read , 256k on write) i have best result on iscsi using transfertl...

Hello

it contains

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\StarNVMeoF\Parameters]
"Auto"=dword:00000000
"BusType"=dword:0000000a
"IoLatencyCap"=dword:00000000
"IoFlags"=dword:00000003

so i just need to add others keys at same level ?

reco on my side <HostNQN> is like nqn.2008-08.com.starwindsoftware.hostnameofserver

on iscsi initiator it's possible to modify

“MaxTransferLength”=dword:00040000
“MaxBurstLength”=dword:00040000
“FirstBurstLength”=dword:00040000
“MaxRecvDataSegmentLength”=dword:00040000

is there a way to do same for nvme initiator ?