- can be used in multi-user/multi-database clusters for resource usage tracking.
- competing databases have such metrics.
The most interesting thing that I could see calculating from these stats would require also knowing how much time was spent waiting on writes and reads on the network. With the cumulative time spent as well as the count of syscalls you can calculate the average latency over any time period between two snapshots. However that would involve adding two gettimeofday calls which would be quite likely to cause a noticeable impact on some architectures. Unless there's already a pair of gettimeofday calls you can piggy back onto?