FIO测试

  • 2014年4月4日
  • 5回复
  • 1603次观点
C
徽章 +5




有人用FIO测试Nutanix但没有诊断VM吗？
当我们测试Nutanix时，我们的主机处理器所有核心都近100％。
我们开始测试3.5.2.1并获取一些磁盘脱机，我们返回它们并升级到3.5.3.1。
在安装结果后第一次（13k IOPS为400 GB磁盘3350），但下一天（所有数据都是冷的）我们有时会有AFWUL重新安装零计数器。对于示例0读/ 0写入。Nutanix是幻灯片上的上部控制台。
它正常吗？
NCC检查告诉一切正常。
对于幻灯片的测试，我们使用100GB磁盘，因此我们应该在一个节点中。
fio config.
> sudo fio read_config.ini
root @ debian：〜＃cat test_vmtools.ini
[阅读]
blocksize = 4k.
filename = / dev / sdb
rw = randread.
直接= 1
缓冲= 0.
ioengine = libaio.
Iodepth = 32.

> sudo fio write_config.ini
root @ debian：〜＃cat test_vmtools.ini
[标记]
blocksize = 4k.
filename = / dev / sdb
rw = RANDWRITE.
直接= 1
缓冲= 0.
ioengine = libaio.
Iodepth = 32.

> sudo fio rw_config.ini
root @ debian：〜＃cat test_vmtools.ini
[阅读]
blocksize = 4k.
filename = / dev / sdb
rw = randread.
直接= 1
缓冲= 0.
ioengine = libaio.
Iodepth = 32.
[标记]
blocksize = 4k.
filename = / dev / sdb
rw = RANDWRITE.
直接= 1
缓冲= 0.
ioengine = libaio.
Iodepth = 32.

有人可以帮我进行测试吗？
<\/a><\/p>
\n
\n
\nDoes anyone test Nutanix with FIO but not with diagnostics VM?
\nWhen we testing Nutanix our processors on host all cores are almost 100 % loaded.
\nWe started test 3.5.2.1 and get some disks maked offline, we return them and upgrade to 3.5.3.1.
\nFor the first time after install results is ok (13k IOPS for 400 Gb disk on 3350), but next day (all data is cold) we have afwul resuls with zero counters sometimes.For example 0 read\/0 write. Nutanix is upper consoles on slide.
\nDoes it normal resuls?
\nncc check tell that everything is ok.
\nFor test on slide we use 100Gb disk so we should be in one node.
\nFio config
\n>sudo fio read_config.ini
\nroot@debian:~# cat test_vmtools.ini
\n[readtest]
\nblocksize=4k
\nfilename=\/dev\/sdb
\nrw=randread
\ndirect=1
\nbuffered=0
\nioengine=libaio
\niodepth=32
\n
\n>sudo fio write_config.ini
\nroot@debian:~# cat test_vmtools.ini
\n[writetest]
\nblocksize=4k
\nfilename=\/dev\/sdb
\nrw=randwrite
\ndirect=1
\nbuffered=0
\nioengine=libaio
\niodepth=32
\n
\n>sudo fio rw_config.ini
\nroot@debian:~# cat test_vmtools.ini
\n[readtest]
\nblocksize=4k
\nfilename=\/dev\/sdb
\nrw=randread
\ndirect=1
\nbuffered=0
\nioengine=libaio
\niodepth=32
\n[writetest]
\nblocksize=4k
\nfilename=\/dev\/sdb
\nrw=randwrite
\ndirect=1
\nbuffered=0
\nioengine=libaio
\niodepth=32
\n
\nCould anyone help me with test?","quoteUsername":"comotoza","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

5回复

加里
秩
UserLevel 1.
徽章 +4
你好，

我们在Nutanix性能实验室中经常在诊断VM之外运行FIO。在测试期间，您获得零IO的事实表明群集中存在错误。请求e打开一个支持案例，以便我们可以弄清楚发生了什么。

- 里奇。
\n
\nWe run fio outside of diagnostics VM quite frequently in the Nutanix performance labs. The fact that you're getting Zero IO's during the test indicates that something is wrong in the cluster. Pleas e open a support case so that we can figure out what's going on.
\n
\n-Gary.","quoteUsername":"gary","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
C
徽章 +5
NCC检查说一切都可以。

5-10分钟的高性能，然后降低性能。
诊断VM获得高性能，但它们仅运行5分钟...



来自诊断VM：
等待热缓存潮湿........................完成。
运行测试“随机读取IOPS”
begin fio_rand_read：2014年3月29日2月29日22:02:25

49495 IOPS.
结束fio_rand_read：2014年3月29日22:04:08

持续时间fio_rand_read：103秒
*******************************************************************************

等待热缓存刷新......完成。
运行测试“随机写入IOPS”
begin fio_rand_write：2014年3月29日星期六22:04:11

26559 IOPS.
结束fio_rand_write：2014年3月29日22:05:54

持续时间fio_rand_write：103秒
\n
\nHigh Performance for 5-10 min, then degraded performance.
\nDiagnostics VMs get high performance but they run only fo 5 min...
\n

<\/a><\/p>
\n
\nFrom diagnostics VMs:
\nWaiting for the hot cache to flush ........................ done.
\nRunning test 'Random read IOPS' ...
\nBegin fio_rand_read: Sat Mar 29 22:02:25 2014
\n
\n49495 IOPS<\/b>
\nEnd fio_rand_read: Sat Mar 29 22:04:08 2014
\n
\nDuration fio_rand_read : 103 secs
\n*******************************************************************************
\n
\nWaiting for the hot cache to flush ... done.
\nRunning test 'Random write IOPS' ...
\nBegin fio_rand_write: Sat Mar 29 22:04:11 2014
\n
\n26559 IOPS<\/b>
\nEnd fio_rand_write: Sat Mar 29 22:05:54 2014
\n
\nDuration fio_rand_write : 103 secs","quoteUsername":"comotoza","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

T.
秩
UserLevel 2.
徽章 +13
每VM多少VMDK磁盘？如果只有一个，您可能正在击中我们的Oplog限制每个Vdisk。

尝试创建多个磁盘，并查看可在降级前扩展时间。

谢谢，
\n
\nTry creating multiple disks and see if that extends the time before degredation.
\n
\nThanks,","quoteUsername":"tonyholland00","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
C
徽章 +5
有两个主要问题：
1.我们的测试是不正确的 - 在Nutanix中我们不能给所有IOPS到一个VM，我们应该使用多个VM与自己的磁盘。
一个VM：2000读/ 500在VM和主机上写入
两个VM：2500Read / 750在主机上写入VM和5000/1500
因此，如果我们想测试Nutanix存储性能，我们应该使用许多VM。
2.在测试期间，由于内存不足的问题，所有请求都被重定向到另一个CVM，因此在测试中崩溃。
Nutanix工程师帮助我们GFLAGS。
代码中没有解决方案尚未在3.5.5和4.0中计划修复。
现在我们没有看到0读写。
前：



后：


我应该如何测试，了解每个VM不是整个群集的表现？
如果我们带着VCCORD导演的服务提供商接受了服务提供商，我们如何保证每VM的IOPS并在SLA中写它？SCIOC和手动每VM IOPS？
\n1. our test was incorrect - in Nutanix we cann't give all IOPS only to one VM, we should use multiple VMs with own disk.
\nOne VM: 2000 read\/500 write in VM and on hosts
\nTwo VMs:2500read\/750 write in VMs and 5000\/1500 on host
\nSo if we want to test Nutanix storage performance we should use many VMs.
\n2. during tests stargate process crash due to an issue with out of memory and all requests were redirected to another CVM.
\nNutanix engineer help us with gflags.
\nThere is no solution in the code yet and the fix is planned for 3.5.5 and 4.0.
\nNow we don't see 0 read and write.
\nbefore:

<\/a><\/p>
\n
\nafter:
\n

<\/a><\/p>
\nHow should I test to understand what performance I can get per VM not whole cluster?
\nIf we are takling about service provider with vCloud Director how we can guarantee IOPS per VM and write it in SLA? SCIOC and manually per VM IOPS?","quoteUsername":"comotoza","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

Dlink7.
UserLevel 4.
徽章 +19
如果您的用例是1VM，1 VDISK确保备份优秀的IO，则可以使用FIO或Iomer进行测试。没有一个系统将伟大的优秀IO。

由于Nutanix在每个节点上具有本地存储控制器，您可以将磁盘LimitsShars与Puartnee资源一起使用。
http://itblooppressure.com/2013/12/02/data-locality-sql-vdi-on-the-same-nutanix-cluster/

此外，您也可以尝试ioAnalyzer，他们有一些预先配置的工作负载，不确定它是否与您的工作匹配。
\n
\nSince Nutanix has local storage controllers on each node you can use disk limitsshares to guartnee resources.
\nhttp:\/\/itbloodpressure.com\/2013\/12\/02\/data-locality-sql-vdi-on-the-same-nutanix-cluster\/
\n
\nAlso you could try IOAnalyzer too, they have some pre-configured workloads, not sure if it matches what your doing or not though.","quoteUsername":"dlink7","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu