Hello, I've been searching in the archives for this bit of information but without much success.
I'd like to monitor and analyse the end-to-end time for various AFS operations (open file, read file, list directory) from the point of view of the client and compare it against the statistics we collect on the servers. This is because 1) I believe that end-to-end client times ultimately correspond to the QoS perceived by users and 2) this could help to disentangle server-side timing issues from anything that happens in between the client and server (including various AFS-internal components, cache performance and ultimately fabric: network, host load etc). I have an impression that the fabric monitoring (which we obviously already have) is not enough. The xstat_cm_test tool reports many metrics but they are sparsely documented (e.g. http://docs.openafs.org/AdminGuide/apc.html#HDRWQ618). Could someone shed some light on how to best get the numbers for my use-case? Another approach which I took was to analyse the sources. As I am new to AFS, I wanted to have a general idea about the design of the client and tried to generate call graphs with tools like cflow for the AFS kernel module, without convincing results yet. Is there any documentation on the internal of client design (linux) and possibly some diagrams or tools/scripts/resources to get them? Anything that could be useful to get a better understanding of how client internally works and which are the relevant available statistics? Many thanks. -- --- Best regards, Kuba
