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

Consider implementing open file caching in text_multifile_backend #142

Open
Lastique opened this issue Mar 4, 2021 · 0 comments
Open

Consider implementing open file caching in text_multifile_backend #142

Lastique opened this issue Mar 4, 2021 · 0 comments

Comments

@Lastique
Copy link
Member

Lastique commented Mar 4, 2021

It was reported that on Windows file open and close operations are much more expensive than on other systems, e.g. Linux. This affects text_multifile_backend, which opens and closes a file on every log record.

Consider implementing a cache of the most recently used files, so that the amount of open/close operations is reduced. The cached entries should have a timeout as well, so that the file is eventually closed if it is not used for too long.

Lastique added a commit that referenced this issue Mar 4, 2021
…dows.

File open/close operations are slow on Windows, which affects
text_multifile_backend.

Related to #142.
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