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

Directory cleanup could be less aggressive #32

Closed
euank opened this issue Dec 19, 2017 · 0 comments
Closed

Directory cleanup could be less aggressive #32

euank opened this issue Dec 19, 2017 · 0 comments
Milestone

Comments

@euank
Copy link
Owner

euank commented Dec 19, 2017

This is a followup to comments on #30 and #6.

Right now, pazi every read of the database (every z) will result in all nonexistent directories being pruned.

In reality, the pruning probably only needs to happen when I directory is actually attempted to be accessed.

Doing it less aggressively has two benefits:

  1. A transient directory which comes and goes can still be zapped to when it's present so long as it wasn't zapped to specifically when it wasn't present
  2. Better performance

As architected, this will not be an easy change; sorting happens at multiple layers for no good reason (and sorting is the enemy of lazyness), the frecency database doesn't clone nor implement interior mutability, etc etc.

@euank euank added this to the v0.0.3 milestone Jan 26, 2018
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

No branches or pull requests

1 participant