[OpenAFS] Re: Advice on a use case

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9CD83CF48E2C00AD99ACDE32
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Timothy:

As Andrew pointed out, the latency of the file server connection is what
will matter most when performing large numbers of small RPCs such as
directory and file creation.  You mention 23,000+ directories and do not
mention the number of files involved.

For rsync to work it must read and stat every single file in every
directory in the tree.  Therefore, the cache must either have enough
room to hold stat info for every directory entry or it must be fetched
from the file server.

You also do not mention where you are performing the rsync.  If you are
doing so locally, you may find that you get better performance by
running an rsync daemon on the AFS file server containing the volumes
you are syncing to.

Since you are syncing and do not care about reading the data back from
AFS, you should be using the cache bypass option.

You mention a desire for OSD.  I'm not sure that OSD is going to help
you if most of your time is spent performing metadata operations and not
actual data transfer.   Based upon what I have heard so far my guess is
that the primary expense is in the metadata operations.

Jeffrey Altman



--------------enig9CD83CF48E2C00AD99ACDE32
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)

iQEcBAEBAgAGBQJQnSxlAAoJENxm1CNJffh46jAH/1TC5+UZcQ5RA2bo3eXxZ9tu
zSDVMm8ZVi16loBBpBu+TS9gZy3+O1FB+QiodI6g6XDBdteh/z91GFej67RArs1x
08WbcKBiHXOpqGwjQXWcA9PYMPweaF/b7pgXf5/9IHMLxNtkVKXQ+3pEWuaxxCBV
Bq3CkBCqioCEW/6hpFY6wnxzJO0S0Ptzkyhs5wjVcjJPkEsQtcKX58a/WD6sjuPo
x0UnKVWIwT/5dS1Cnueco65xRniiosSo7q8sedFWo7v+dLkZ3TLTdto6PWm66Djx
mZuLnSfxF76f6flam7xn4QVm3I9YBMMD2rVMbO0NA0zE4+eCUmE3DvGL9m1V/B0=
=14io
-----END PGP SIGNATURE-----

--------------enig9CD83CF48E2C00AD99ACDE32--