Date: Thu, 15 Sep 2016 07:53:19 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 212681] I/O is slow for FreeBSD DOMu on XenServer Message-ID: <bug-212681-23905-KUKffyvjMw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-212681-23905@https.bugs.freebsd.org/bugzilla/> References: <bug-212681-23905@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212681 --- Comment #7 from rainer@ultra-secure.de --- The hardware is HP DL380 Gen 8 servers with 600 or 900 GB SAS disks, running off a HW RAID controller. On local storage, the realworld-test is even slower. I can't run the dc3dd test here and it's apparently a bit more complicated = now to create VMs from a template on local storage now that we have completely eliminated it from our offerings. (server </srv>) 0 # time dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D2= 0480=20 20480+0 records in 20480+0 records out 1342177280 bytes transferred in 22.239869 secs (60350053 bytes/sec) dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D20480 0.04s user 6.20s sy= stem 28% cpu 22.255 total (server </srv>) 0 # time dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D2= 0480 20480+0 records in 20480+0 records out 1342177280 bytes transferred in 38.072567 secs (35253133 bytes/sec) dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D20480 0.05s user 24.30s s= ystem 63% cpu 38.374 total (server </srv>) 0 # time dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D2= 0480 20480+0 records in 20480+0 records out 1342177280 bytes transferred in 5.782933 secs (232092820 bytes/sec) dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D20480 0.05s user 2.27s sy= stem 38% cpu 6.021 total (server </srv>) 0 #=20 (server </srv>) 0 #=20 (server </srv>) 0 #=20 (server </srv>) 0 # time dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D2= 0480 20480+0 records in 20480+0 records out 1342177280 bytes transferred in 7.891797 secs (170072452 bytes/sec) dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D20480 0.00s user 2.26s sy= stem 27% cpu 8.141 total (server </srv>) 0 #=20 (server </srv>) 0 # time dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D2= 0480 20480+0 records in 20480+0 records out 1342177280 bytes transferred in 12.598706 secs (106532947 bytes/sec) dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D20480 0.02s user 2.37s sy= stem 18% cpu 12.845 total (server </srv>) 0 #=20 (server </srv>) 0 # time dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D2= 0480 20480+0 records in 20480+0 records out 1342177280 bytes transferred in 7.917661 secs (169516892 bytes/sec) dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D20480 0.03s user 2.23s sy= stem 27% cpu 8.144 total (server </srv>) 0 # time dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D2= 04800 204800+0 records in 204800+0 records out 13421772800 bytes transferred in 147.423047 secs (91042568 bytes/sec) dd if=3D/dev/zero of=3Dtest.dat bs=3D64k count=3D204800 0.18s user 22.60s = system 15% cpu 2:27.69 total dc3dd is just a tool to securely wipe a disk. I found, because it takes the filesystem out of the equation, that it's a n= ice benchmarking tool. Also, the results of dc3dd correlate directly with the results of the testc= ase (in PHP) that the customer has built. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212681-23905-KUKffyvjMw>