Skip to content
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

issue-695: revert bulk loading of attributes #702

Merged
merged 2 commits into from
May 22, 2022

Conversation

faenschi
Copy link
Contributor

@faenschi faenschi commented Apr 20, 2022

@fstab closes #695

Signed-off-by: Angela Stempfel <angela.stempfel@postfinance.ch>
@faenschi faenschi force-pushed the fix-attribute-loading branch from 8a28d70 to 25c148a Compare April 20, 2022 09:09
Copy link
Member

@fstab fstab left a 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 the PR. I read the old comments in #238 when we switched from loading individual attributes to bulk loading. It seems like this resulted in a significant performance improvement.

So I'm wondering: Can we keep the bulk loading as default, but revert to attribute-by-attribute loading when an Exception is thrown?

Interestingly that's exactly what was in the original proposal in #238 but it was replaced with "just log the failure and continue".

Signed-off-by: Fabian Stäber <fabian@fstab.de>
@fstab fstab merged commit 3a124ec into prometheus:master May 22, 2022
@fstab
Copy link
Member

fstab commented May 22, 2022

Hi, I changed the code so that 1-by-1 loading of attributes is only used as a fallback if bulk loading fails.

I'm planning to include this in the next release.

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

java.rmi.UnmarshalException while scraping metrics
2 participants