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

memoize DiffFieldReader.ReadField #15663

Merged
merged 1 commit into from
Aug 3, 2017
Merged

Conversation

jbardin
Copy link
Member

@jbardin jbardin commented Jul 28, 2017

The field reader code path is extremely inefficient, but refactoring
it all is much to invasive a change at the moment.

Have DiffFieldReader internally cache results for ReadField.

This is a reduced version of #15641. The DiffFieldReader is the hot entry point, and localizing the caching to a particular instance seems much safer.

The field reader code path is extremely inefficient, but refactoring
it all is much to invasive a change at the moment.

Have DiffFieldReader internally cache results for ReadField.
Copy link
Contributor

@apparentlymart apparentlymart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable to me.

Given that helper/schema changes have historically had surprising side-effects, I'd prefer to hold merging this until after the 0.10.0 release.

@dshafik
Copy link

dshafik commented Jul 28, 2017

I can confirm that this does indeed solve the issue raised in #15641, thanks! 🥇

@jbardin jbardin merged commit 8a8b431 into master Aug 3, 2017
@jbardin jbardin deleted the jbardin/diff-field-reader branch August 3, 2017 17:25
@ghost
Copy link

ghost commented Apr 8, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants