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

don't cache varctx (rare operation) #110

Closed
wants to merge 1 commit into from
Closed

don't cache varctx (rare operation) #110

wants to merge 1 commit into from

Conversation

jonsterling
Copy link
Collaborator

@jonsterling jonsterling commented Feb 26, 2018

This operation used to be very frequent in RedPRL (so frequent that I think there was no term that did not eventually have this function called on it repeatedly!) so it helped to cache it, but now it is extremely rare, with some changes I'm making to RedPRL now. So, it actually hinders performance to cache this.

Close #109

@jonsterling
Copy link
Collaborator Author

Actually, I found another place where varctx is called: in checkb.

Surprisingly, this is still a performance win in RedPRL, even though we must be calling varctx again and again still.

But these changes are probably going to be superseded anyway by a rewrite of this library that I'm undertaking now.

@favonia
Copy link
Contributor

favonia commented Feb 26, 2018

Should we wait, then? I trust your judgment but am confused by your message.

@jonsterling
Copy link
Collaborator Author

@favonia I want to try out some more stuff before we merge anything to do with this.

@jonsterling jonsterling closed this Jun 6, 2021
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.

Consider not caching varctx
2 participants