aiperf Total requests fired discrepancy

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
performance

Research direction

No file or test is named. Start by tracing aiperf's request accounting for duration-bound waves and in-flight cancellations, then identify how “Total requests fired” is calculated. Done means the reported total is no longer misleading when requests are cancelled, with coverage for that scenario.

Written by the indexing model from the issue text.

Description

misleading when some in-flight requests cancelled for duration bound waves

Dominant language
Python
Stars
0
Forks
1
No merged PRs in 30d

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 aws-samples/sample-InferenceBenchmarker

All issues in aws-samples/sample-InferenceBenchmarker

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.