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

ahead/behind can get really slow #5

Open
evansolomon opened this issue Apr 30, 2013 · 2 comments
Open

ahead/behind can get really slow #5

evansolomon opened this issue Apr 30, 2013 · 2 comments

Comments

@evansolomon
Copy link
Member

Anecdotally it seems like this happens in repos with long history, but haven't tested it yet. Just noticed it this morning.

For example, it seems to add about 800ms to loading a prompt in the WordPress repo.
@evansolomon
Copy link
Member Author

@koop does the new caching stuff in Impromptu help this?

@koop
Copy link
Member

koop commented May 6, 2013

Close — I need to add a blocking option so the information will always be up to date. I'll try to get to it in the next day or so.

On the git side, we need a method to access the latest commit hash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@koop @evansolomon