Consider implementing open file caching in text_multifile_backend

Open
#142 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp

Research direction

Start by locating text_multifile_backend and reviewing how it opens and closes files for each log record. Determine the cache behavior, most-recently-used policy, and idle timeout needed to reduce Windows open/close operations. Done means unused cached files are eventually closed while repeated logging reuses open files.

Written by the indexing model from the issue text.

Description

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.

Dominant language
C++
Stars
211
Forks
114
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boostorg/log

All issues in boostorg/log

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.