Open patrickbrophy opened 2 months ago
I've been investigating this. I've discovered that the process statistics that are reported by XRootD are faulty in that they report zeros for the amount of seconds for both user and system. In addition, the values for microseconds doesn't make a whole lot of sense. I've attempted to remedy this by making a getrusage
sys call from the Pelican process, but the problem is that getrusage
requires that the subprocess it is being called upon is terminated. So for now this an issue with XRootD.
What's the status on this? Has a corresponding issue been opened in the XRootD repo?
I had forgotten to make an issue for this. I can get started on writing one up.
There is now an issue
We should be tracking XRootD CPU usage, considering that it is a core process within Pelican. Process time statistics are provided via the summary packets. Documentation here. This would probably require to a new case to the
HandleSummaryPacket
function. Getting a percentage of CPU usage would require some simple arithmetic.