Hardcoded queue capacity 100 should be configurable via --queue-size #105

Closed
opened 2026-07-21 16:20:13 +02:00 by TapTap · 1 comment
Owner

Description

Both pipeline queues (scanner→loader and loader→sender) are hardcoded to capacity 100 in client_send.c:521-522. This is not configurable and may be suboptimal for large transfers.

Location

src/client/client_send.c:521-522

Suggested Fix

Add --queue-size <n> flag (default: 100). Use it when creating the pipeline queues. The config value should be stored in Config.

Severity

medium

Category

feature

Sub-Agent

feature-scout (FS-11)


This issue was automatically generated by the issue-creator agent.

## Description Both pipeline queues (scanner→loader and loader→sender) are hardcoded to capacity 100 in `client_send.c:521-522`. This is not configurable and may be suboptimal for large transfers. ## Location src/client/client_send.c:521-522 ## Suggested Fix Add `--queue-size <n>` flag (default: 100). Use it when creating the pipeline queues. The config value should be stored in `Config`. ## Severity medium ## Category feature ## Sub-Agent feature-scout (FS-11) --- _This issue was automatically generated by the issue-creator agent._
Author
Owner

Fixed in PR #148 — merged into main on 2026-07-29.

Fixed in PR #148 — merged into main on 2026-07-29.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: TapTap/FastSync#105