From drbd-user  Thu Jun 05 18:10:25 2014
From: Arnold Krille <arnold () arnoldarts ! de>
Date: Thu, 05 Jun 2014 18:10:25 +0000
To: drbd-user
Subject: Re: [DRBD-user] Extremely high latency problem
Message-Id: <20140605201025.77154e99 () xingu ! arnoldarts ! de>
X-MARC-Message: https://marc.info/?l=drbd-user&m=140199184920850
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============7852890944534335101=="

--===============7852890944534335101==
Content-Type: multipart/signed; micalg=PGP-SHA256;
 boundary="Sig_/4nKqlHQytXQwC3fj5.q.7bm"; protocol="application/pgp-signature"

--Sig_/4nKqlHQytXQwC3fj5.q.7bm
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Thu, 5 Jun 2014 09:30:37 -0700 Bret Mette
<bret.mette@dbihosting.com> wrote:
> dd if=3D/dev/zero of=3D./testbin  bs=3D512 count=3D1000 oflag=3Ddirect
> 12000 bytes (512 kB) copied, 0.153541 s, 3.3 MB/s
>=20
> This was run against /root/testbin which is /dev/md1 with no LVM or
> DRBD
>=20
>=20
>=20
> dd if=3D/dev/zero of=3D./testbin  bs=3D512 count=3D1000 oflag=3Ddirect
> 512000 bytes (512 kB) copied, 32.3254 s, 15.8 kB/s
>=20
> This was run against /mnt/tmp which is DRBD /dev/drbd2 backed by an
> LVM logical volume, with the logical volume backed by /dev/md127 while
> /dev/drbd2 was in the connected state

Change your dd-parameters for meaningful results!

Disks are read and written in 4k junks. Writing 512 bytes means
actually reading 4k, replacing the 512 bytes to write, write 4k. Slow
by default!

Use at least 4k junk size for dd. And use a higher count, 4k * 1000 is
roughly 4M. Most disks today have a cache bigger then that.

And when you only run your test for 0.15 seconds, you don't even out
background-stuff from the os.

Using dd for performance tests should result in files of several
gigabytes size.

The next question is whether you really want to optimize for linear
access which dd kind of measures. Better use a tool like dbench to test
random-access which is a 99.99999% (*) more common usage pattern. Apart
from copying big disk-images or video files, every other use case (even
using disk-images for virtual machines or editing audio-/video-files)
is random access. That means seeking on the harddisk.

Have fun,

Arnold

(*) Could be my estimation is a few 9s short...

--Sig_/4nKqlHQytXQwC3fj5.q.7bm
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iF4EAREIAAYFAlOQspEACgkQtuvagsE+DE6qvwD/XCPr8p5rCWs6gKVpDAZWTdwO
5DqhEVGQArtKw0RQqSUBAIBSTJrN9LPChu/53LVGu6WUaZhKVi3sYP17SabqGM1X
=OzVl
-----END PGP SIGNATURE-----

--Sig_/4nKqlHQytXQwC3fj5.q.7bm--

--===============7852890944534335101==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user

--===============7852890944534335101==--