[OpenAFS] Transfer rates under OpenAFS client for Windows
Jeffrey Altman
jaltman@your-file-system.com
Wed, 04 Jul 2012 00:37:10 -0400
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC553C7C3B55B6604DC6DDFCA
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 7/3/2012 8:30 PM, Jeffrey Altman wrote:
> On 7/3/2012 4:27 PM, Danko Antolovic wrote:
>=20
>> My first question is why copying from the client to the file server is=
>> so much slower (by a factor of 2 or 3) than the other way around. The=
>> other question is why the network utilization, at least as reported
>> under Windows, never approaches the line rate, even at quiet times, bu=
t
>> rather stays below the caps of 70 and 30 percent.
>=20
> It won't go any faster with the OpenAFS RX implementation.
to provide additional details. The windows cache manager stores a file
in 4K buffers. In order to write a chunk to the file server, the client
must collect and lock the appropriate set of buffers. Then the cache
manager must obtain a set of packet buffers from RX and copy the data
into the packet buffers. The packet buffers and file buffers are not
aligned so the copies are quite expensive. Then the packet data must be
processed for authentication and perhaps encryption. Finally the packet
data is copied once more into the network packet buffers.
The OpenAFS rx stack does not provide a mechanism by which the cache
manager can lend the file buffers for use as packet buffers. Such an
implementation cannot be implemented in the existing RX implementation
because rx objects are not reference counted.
This process is much less efficient than the unix cache manager but is
more flexible. The AFS cache to Windows system (page) cache interface
is very fast and can support up to 800MB/second transfers. The rx
interface is the current bottleneck.
Jeffrey Altman
--------------enigC553C7C3B55B6604DC6DDFCA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
iQEcBAEBAgAGBQJP88h5AAoJENxm1CNJffh4iHoIANFO/fP8F+NbqREct4dVoHOp
i59qWe8lWSpJVHcFJUkuHcnJ85gGGSu0XKj00IeMdcRbZm2nuAjvQhT1f8hvg2RZ
IrZo5lefDCHiQ9UFHNM6N31b2Ddz4CZMFOaDsk/t5vTO1feSqTrBjEhf5zgOcfdn
IXDAxVDefLIiwiM87hD/hCkyMZ/ASmLJ90SiZ9jPcZYopu0er702W6ISioR4z3tD
HQs8zvp42bF7FZZKh5iT5eLCw3GmgNisml7FAdY6Y0ffykGHfQjiZoWLGtCfXHu3
IWKHoiuhcxYN7mYToe5HxwGGvPC6lPBtq2d0G3ZLR6Br88ZBkjW6jlh+jQLyVXQ=
=ntU3
-----END PGP SIGNATURE-----
--------------enigC553C7C3B55B6604DC6DDFCA--