-
-
Notifications
You must be signed in to change notification settings - Fork 549
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
atuin history gc? #2015
Comments
It seems like its taking almost 0.5 to 1 second when I press As a proxy for timing, it takes about 5 seconds to run
|
Looks like my slowdown is likely related to getting the unique set of commands: See #475 |
I have the same issue. I am actually running "atuin import zsh" multiple times in order to incrementally save my zsh history before I actually really start using atuin and commands are added multiple times. Some sort of deduplication based on the time and command would be extremely appreciated. |
Any feedback on this ticket at all? |
@AlJohri in response to your issue, I'd suggest trying to craft a If that is not possible, then I'm afraid the only real way forwards would be to delete and start from scratch :/ Due to how the importers work at the moment, it's not that straightforward to correctly identify duplicate imports vs commands that have been ran a few times. Otherwise, if you're able to profile the startup/searching with your data, I'd really appreciate it! You may find that the prefix search mode performs much faster.
@zuzzurro I'm afraid this use case isn't supported. Importing is for migrating old data to Atuin, and not for keeping Atuin up-to-date. Given that the original data soruce doesn't always have enough information to effectively de-dupe, it's not that straightforward. Your request isn't quite the same as the OP, so I'd appreciate you opening a new issue if there's anything you wish to have help with. |
I asked before trying to solve the issue myself.... |
Thanks. As I said my personal perspective is probably skewed by the fact that in zsh I don't care about saving multiple copies of the same command... so no hard feelings at all if it nobody else cares about it. |
What if we ignored the distinction between commands that have been run a few times and duplicate imports and deduplicated it anyway? That way I still have at least 1 copy of every command I have ever run accessible through prefix or exact match search. And I can build up the more frequent commands again over time into the history. Is this possible to do? Are there any implications with doing this that I am missing? |
Is there a guide on profiling atuin I can follow? Or some high level steps. |
I seem to have accidentally re-run
atuin import zsh
after already using atuin for a period of time. I installed atuin on a new computer and kept syncing and was getting 0 results. I wasn't sure what was going on until I realized that the new installation was using the sync v2. I have since upgraded all installations to use sync v2, however as part of trying to figure out what was going on, I had re-run theatuin import zsh
command and then runatuin sync
. This appears to have doubled the size of my history from 150k records to 300k records.Is there anyway I can "garbage collect" down to a list of unique entries and clean up my atuin history?
The text was updated successfully, but these errors were encountered: