-
-
Notifications
You must be signed in to change notification settings - Fork 63
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 go through all git objects? #77
Comments
Hi, may i ask how you installed ripasso and what version you are running? Is might be a duplicate of this bug: #57 |
I am looking the version up tonight when I am back in front of my computer.
I did install it on arch with yay ripasso-recursive
Niels
… On 21. Dec 2019, at 09:11, Alexander Kjäll ***@***.***> wrote:
Hi, may i ask how you installed ripasso and what version you are running? Is might be a duplicate of this bug: #57
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I installed ripasso-git from the AUR. pacman -Qi ripasso-git:
|
Thanks, then it's not a duplicate. I need to write some performance tests and do some benchmarking in order to have a framework around doing performance improvements. Thanks for the report. |
I reproduced this, and I think there is two ways to improve this. The first is to improve the handling of populating the list of passwords, right now the logic looks like this: Get a list of password files, for each fil: parse the git repository to obtain metadata. If we instead just parsed the git repository once, and obtained information about all files while doing so, then the startup time would scale sort of linear instead of quadratically. Another avenue for improvement would be to only calculate the meta data when displayed on screen, but that requires an improvement in the cursive library, I have opened a feature request with them here: gyscos/cursive#414 |
Another factor is that the git blame code in libgit2 isn't as fast as git's own code: libgit2/libgit2#3027 |
…password list. In order to have a baseline when fixing the performance problems reported in #77
fixed in 4e3b377 |
I tried to start ripasso after a fresh install but always interrupted it because it just ate up my cpu (1 core at 100%) and nothing happened. Then I started it with strace and see tons of calls like this:
Apparently ripasso goes through all the files in .git for whatever reason at least on the first start. Since I am using pass for a couple of years and with several hundreds passwords I expect it to be huge…
The text was updated successfully, but these errors were encountered: