-
Notifications
You must be signed in to change notification settings - Fork 439
Cache prometheusize rename between scrapes #1080
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for your contribution. Please
- Fix failing tests.
- Sign the CLA
Hi @vigno88 looks like tests are still failing - also looks like the profile you shared was from before the change - will be nice to have both to see how they compare. |
Hi, thanks for the quick response. I'll take a look at the tests and yes i will provide a new profile. Nathan AV |
Hi, please also make sure that it's thread-safe. |
i've signed the CLA a lot of time last week and I tried again today. It says that the signature was made, but the status of the issue doesn't update.. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1080 +/- ##
==========================================
- Coverage 70.88% 65.50% -5.39%
==========================================
Files 28 29 +1
Lines 3569 3073 -496
==========================================
- Hits 2530 2013 -517
- Misses 904 922 +18
- Partials 135 138 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There are other changes is this profile, but this show the cpu usage of prometheusize after the changes. |
All the test have passed, and the signature for my account has passed (vigno99 is the user of my computer) |
Thanks a lot for your contribution, @vigno88. I'll check with our internal QA team about testing this, and then we can merge. |
vigno99 looks like an autogenerated git user on my work computer. It's not linked to any github account.. I can't log to anything with it |
After profiling the exporter because it had a somewhat high cpu usage, it reported that the regexp operations in this function accounts for more than 10% of the cpu time.
More precisely, the first call to prometheusize uses 3.79%, the second 5.86% (in exporter.MakeMetrics) and lastly it 1.03% (in exporter.MakeRawMetrics)
This all goes to zero if we cache them.