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

Feature request: Optimize initialization for large databases #5019

Closed
ericmock opened this issue Dec 17, 2022 · 2 comments
Closed

Feature request: Optimize initialization for large databases #5019

ericmock opened this issue Dec 17, 2022 · 2 comments
Labels
bug Something isn't working cli performance

Comments

@ericmock
Copy link

I have a small script in my .bashrc file that shows the current branch in the command prompt. Thus, every time a prompt is generated, dolt branch --show-current is run. This takes about 60 seconds for a database the size of the housing bounty database (~100GB ?). Thus, whenever this database is in a sub-directory, working on the command line becomes a PITA.

As a quick fix, I'm wondering if dolt needs to be fully initialized for every command. Could this be bypassed for things like branch, which really doesn't make sense to even run outside the database directory?

@timsehn timsehn added bug Something isn't working performance cli labels Dec 19, 2022
@timsehn
Copy link
Sponsor Contributor

timsehn commented Feb 10, 2023

This is a duplicate of #3629. Resolving in favor of that one.

@timsehn timsehn closed this as completed Feb 10, 2023
@lizkimble
Copy link

i'd like to revisit this, it's so useful knowing what branch you're on by looking at the command prompt, but when the database is large it really becomes a painfully slow

is there some other way to get the current branch, like from the repo_state.json file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cli performance
Projects
None yet
Development

No branches or pull requests

3 participants