You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been troubleshooting a node implementation that is currently using your lib to expose prometheus metrics and using clinicJS tool notices that almost 80% of total cpu usage time is spend in T _host_get_clock_service call. Already updated lib version to 14.0.1, but issues continues to be present.
Clinic Flamechart is this one:
Looking at your source code it can be related with Date.now(); requests performed in lib/timeWindowQuantiles.js or lib/metrics/processStartTime.js.
Do you have any suggestion on how to troubleshoot these issues and try to mitigate them?
Many Thanks for your help
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. I'm hoping to look into this this month, but please don't let that stop anyone else from taking a look if they have time before I do.
I have been troubleshooting a node implementation that is currently using your lib to expose prometheus metrics and using clinicJS tool notices that almost 80% of total cpu usage time is spend in T _host_get_clock_service call. Already updated lib version to 14.0.1, but issues continues to be present.
Clinic Flamechart is this one:
Looking at your source code it can be related with Date.now(); requests performed in lib/timeWindowQuantiles.js or lib/metrics/processStartTime.js.
Do you have any suggestion on how to troubleshoot these issues and try to mitigate them?
Many Thanks for your help
The text was updated successfully, but these errors were encountered: