[Top] [All Lists]

Re: Pid: 8345, comm: rsync Not tainted #1

To: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Subject: Re: Pid: 8345, comm: rsync Not tainted #1
From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
Date: Wed, 27 Oct 2010 09:00:06 +0200
Cc: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20101027080454.31a59a3c@xxxxxxxxxxxxxx>
References: <4CC67450.9020602@xxxxxxxxxxxx> <4CC6B56B.7020007@xxxxxxxxxxxx> <20101026132505.6af29d5d@xxxxxxxxxxxxxxxxxxxx> <201010270124.44846@xxxxxx> <20101027080454.31a59a3c@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101006 Thunderbird/3.0.9
So what values do you recommand in general for iSCSI on Serverside and which values on iSCSI client side?


Am 27.10.2010 08:04, schrieb Emmanuel Florac:
Le Wed, 27 Oct 2010 01:23:35 +0200 vous écriviez:

BTW: any recommendations for these tuning knobs on VM-ized servers?
What should be set in the VMs and what on the host?

 From my experience, using iSCSI as the transport to export lvs to the
VMs, the best performance is reach by setting scheduler to noop and
queue depth on the target and the VM; but setting the readahead only on
the VM side.

For different configurations, as usual, YMMV.

<Prev in Thread] Current Thread [Next in Thread>