Integrate IOPS / bandwidth limiting with backpressure

Open
#1,343 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
distributed-systems, performance

Research direction

Start by reading RFD 445 §4.1, especially the section on IOPS and bandwidth limits not causing backpressure. Then locate Crucible’s guest backpressure and capacity-limiting entry points; the work is done when limited IOPS and bandwidth also prevent arbitrary guest-side job buffering.

Written by the indexing model from the issue text.

Description

As part of Crucible capacity management, we want IOPS and bandwidth limiting.

Right now, those limits are not integrated into the backpressure system, meaning the guest will buffer arbitrarily many jobs (before backpressure), then trickle them into the upstairs at an IOPS/bandwidth-limited rate. Buffering arbitrarily many jobs is bad!

See RFD 445 § 4.1

Dominant language
Rust
Stars
260
Forks
34
Avg merge
2d 1h
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

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 oxidecomputer/crucible

All issues in oxidecomputer/crucible

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.