Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[PERF] Long per-author refreshes can occupy every command thread and starve short commands

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

Maintainers usually reply within 7 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
43/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, docker

Research direction

Start at the command scheduling and thread management code; the issue does not name specific files or tests. Trace how RefreshAuthor commands occupy worker threads while RSS sync, downloads, and imports are queued, then compare the proposed thread reservation and per-command concurrency cap. Done means long refreshes can no longer starve those shorter or higher-priority commands.

Written by the indexing model from the issue text.

Description

enhancement

Problem

Command priority ordering exists, but N long RefreshAuthor commands (an author with ~5,000 books takes minutes) can still occupy all N command threads while RSS sync, download processing and imports wait. Raising the thread count (#222) reduces but does not remove this.

Suggested direction

Reserve one or two threads for non-long-running or high-priority commands, or cap concurrent commands of the same name. Found while reviewing #222.

Dominant language
C#
Stars
664
Forks
48
Avg merge
3d 5h
Merged PRs (30d)
1

Getting set up

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 Chaptarr/chaptarr

All issues in Chaptarr/chaptarr

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.