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

Speed improvement keeping files open #2

Open
HerManNav opened this issue Jul 6, 2023 · 0 comments
Open

Speed improvement keeping files open #2

HerManNav opened this issue Jul 6, 2023 · 0 comments
Labels
performance Makes the code go "brrrr"

Comments

@HerManNav
Copy link
Collaborator

A posible improvement for performance could consist of keeping the file open until the user called a specific method to close the file when all the modifications have been performed. This method SHOULD be called also in the destructor of the dirB instance!

The main drawback of this approach is that the file wouldn't be accessible by other applicactions while the instance of the dirB lasted.

A third approach is to let the user select between these 2 modes (performance vs accessibility modes).

@HerManNav HerManNav transferred this issue from another repository Mar 7, 2024
@HerManNav HerManNav added the performance Makes the code go "brrrr" label Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Makes the code go "brrrr"
Projects
None yet
Development

No branches or pull requests

1 participant