Re: 4x lower IOPS: Linux MD vs indiv. devices - why?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 23.01.2017 um 20:06 schrieb Kudryavtsev, Andrey O:
Hi Tobias,
Yes, “imsm” is in generic release, you don’t need to go to the latest or special build then if you want to stay compliant. It’s mainly a different layout of a raid metadata.

Your findings follow my expectations, for QD1 sync engine does good results. Can you try libio with QD4 and 2800/4 jobs?
Most of the time I’m running Centos7 either with 3.10 or latest kernel depends of the scope of the testing.

Changing sector to 4k is easy, this can really help. see DCT manual, it’s there.
This can be relevant for you https://itpeernetwork.intel.com/how-to-configure-oracle-redo-on-the-intel-pcie-ssd-dc-p3700/



It doesn't work with LBAFormat=3 either:

oberstet@svr-psql19:~/scm/parcit/RA/user/oberstet$ sudo isdct start -nvmeformat -intelssd 0 \
>   LBAFormat=3 \
>   SecureEraseSetting=0 \
>   ProtectionInformation=0 \
>   MetaDataSettings=0
WARNING! You have selected to format the drive!
Proceed with the format? (Y|N): y
Formatting...

- Intel SSD DC P3608 Series CVF8551400324P0DGN-1 -

Status : Interrupted system call

oberstet@svr-psql19:~/scm/parcit/RA/user/oberstet$

oberstet@svr-psql19:~/scm/parcit/RA/user/oberstet$ sudo isdct show -all -intelssd 0 | grep LBA
LBAFormat : 0
MaximumLBA : 3907029167
NativeMaxLBA : 3907029167
NumLBAFormats : 6

-----

And using exactly the same parameters as the article above:

oberstet@svr-psql19:~/scm/parcit/RA/user/oberstet$ time sudo isdct start -nvmeformat -intelssd 0 \
>   LBAFormat=3 \
>   SecureEraseSetting=2 \
>   ProtectionInformation=0 \
>   MetaDataSettings=0
WARNING! You have selected to format the drive!
Proceed with the format? (Y|N): y
Formatting...

- Intel SSD DC P3608 Series CVF8551400324P0DGN-1 -

Status : Interrupted system call


real	0m26.901s
user	0m0.048s
sys	0m0.032s
oberstet@svr-psql19:~/scm/parcit/RA/user/oberstet$


----

I see the following in kernel log:

[417528.128501] nvme nvme0: I/O 0 QID 0 timeout, reset controller
[417786.440977] nvme nvme0: I/O 0 QID 0 timeout, reset controller


What should I do?

Thanks alot,
/Tobias
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux