1. On my version it is the the average; it sums times in the C code and then the nstelemetry.adp computes sum/hits. It is per url
2. entries is the current number of entries in the cache, flushed is the total number deleted or replaced, hits is the count of successful gets, misses is the number of unsuccessful gets and hitrate is the percentage of time the cache was useful. 86% hitrate is reasonably good.
3. I dont think that number of busy locks is an issue. It is a count so really as a fraction of the number of locks taken that is minuscule.
If you are interested in tuning your server you should look for the
article Jim Davidson wrote about Digital City's use of aolserver at http://aolserver.com/docs/tcl2k/html/index.htm
also, http://www.arsdigita.com/asj/tuning/ and
http://aolserver.com/documentation/tuning.adp have some useful
suggestions.
