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.

Sign up for GitHub

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

Jump to bottom

In DumpMain, class resolving takes 2/3 of execution time when queue value type not present #644

Closed
alamar opened this issue Apr 8, 2024 · 1 comment
Closed

In DumpMain, class resolving takes 2/3 of execution time when queue value type not present #644

alamar opened this issue Apr 8, 2024 · 1 comment
Assignees
@alamar

Comments

@alamar
Copy link
Contributor

alamar commented Apr 8, 2024

Probably elsewhere. It turns out that Class.forName() is an expensive operation and should not be done repeatedly. Let us try caching the absense of the value to avoid redoing this lookup on every entry.
@alamar alamar self-assigned this Apr 8, 2024
@alamar alamar transferred this issue from OpenHFT/Chronicle-Wire Apr 8, 2024
alamar pushed a commit that referenced this issue Apr 8, 2024
Cache resolution failures to avoid repeated attempts
5c73aec 
closes #644
@alamar alamar mentioned this issue Apr 8, 2024
Merged
peter-lawrey pushed a commit that referenced this issue Apr 12, 2024
@alamar @peter-lawrey
Cache resolution failures to avoid repeated attempts (#645)
e8dded8 
closes #644
@hft-team-city
Copy link
Collaborator

Released in Chronicle-Core-2.25ea14, BOM-2.25ea45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alamar alamar

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alamar @hft-team-city