domverse/photoanalyzer
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

US07-06 — Validate Performance and Resource Bounds #43

New Issue
Closed
opened 2026-07-13 13:10:53 +02:00 by domverse · 3 comments
domverse commented 2026-07-13 13:10:53 +02:00
Owner
Copy Link

Source specification: delivery_backlog/stories/US07-06-performance.md

US07-06 — Validate Performance and Resource Bounds

Epic: E07

As an operator, I want measured performance and bounded resource use so large libraries
remain responsive and do not exhaust memory, disk, handles, or queues.

Acceptance criteria

  • Agreed budgets cover API latency, throughput, RSS, open files, WAL, queues, cache,
    disk reserve, and event delivery at 25k, 100k, and 500k synthetic assets.
  • Duplicate clusters with thousands of members remain usable and paged.
  • Multi-hour work plus browsing, cancellation, retry, backup, and cache eviction shows
    no unbounded growth or starvation.
  • Budget exceptions are measured, documented, and approved before release.

Automated tests

  • Repeatable load/soak commands export machine-readable metrics and fail budget breaches.
  • CI runs a short profile; scheduled infrastructure runs the full soak matrix.

Dependencies

  • US07-04, US07-05
Source specification: [delivery_backlog/stories/US07-06-performance.md](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/stories/US07-06-performance.md) # US07-06 — Validate Performance and Resource Bounds Epic: [E07](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/E07-hardening-release.md) As an operator, I want measured performance and bounded resource use so large libraries remain responsive and do not exhaust memory, disk, handles, or queues. ## Acceptance criteria - Agreed budgets cover API latency, throughput, RSS, open files, WAL, queues, cache, disk reserve, and event delivery at 25k, 100k, and 500k synthetic assets. - Duplicate clusters with thousands of members remain usable and paged. - Multi-hour work plus browsing, cancellation, retry, backup, and cache eviction shows no unbounded growth or starvation. - Budget exceptions are measured, documented, and approved before release. ## Automated tests - Repeatable load/soak commands export machine-readable metrics and fail budget breaches. - CI runs a short profile; scheduled infrastructure runs the full soak matrix. ## Dependencies - US07-04, US07-05
domverse added this to the E07 — Hardening and Release milestone 2026-07-13 13:10:53 +02:00
domverse added the area/backendtype/hardeningpriority/normalarea/testing labels 2026-07-13 13:10:53 +02:00
domverse added a new dependency 2026-07-13 13:11:33 +02:00
#41 US07-04 — Prove Concurrency and Crash Recovery
domverse added a new dependency 2026-07-13 13:11:33 +02:00
#42 US07-05 — Deliver Backup and Operational Recovery
domverse added a new dependency 2026-07-13 13:11:35 +02:00
#44 US07-07 — Automate Full Release Acceptance
domverse added this to the Photo Analyzer Delivery project 2026-07-13 13:19:48 +02:00
domverse added the status/backlog label 2026-07-13 13:52:57 +02:00
domverse added status/in-progress and removed status/backlog labels 2026-08-17 21:14:53 +02:00
domverse self-assigned this 2026-08-17 21:14:53 +02:00
domverse commented 2026-08-17 21:14:54 +02:00
Author
Owner
Copy Link

Claimed for implementation on branch us/US07-06-validate-performance-and-resource-bounds.

Claimed for implementation on branch `us/US07-06-validate-performance-and-resource-bounds`.
domverse added status/review and removed status/in-progress labels 2026-08-17 21:51:53 +02:00
domverse commented 2026-08-17 21:51:54 +02:00
Author
Owner
Copy Link

Submitted for review: #93

Tests passed:

  • work_item/scripts/python -m unittest discover -s work_item/tests -v
  • work_item/scripts/python -m pytest tests -q
  • work_item/scripts/python -m pytest tests/integration/test_performance_budgets.py -q
Submitted for review: https://git.domverse-berlin.eu/domverse/photoanalyzer/pulls/93 Tests passed: - `work_item/scripts/python -m unittest discover -s work_item/tests -v` - `work_item/scripts/python -m pytest tests -q` - `work_item/scripts/python -m pytest tests/integration/test_performance_budgets.py -q`
domverse added status/done and removed status/review labels 2026-08-17 21:52:06 +02:00
domverse commented 2026-08-17 21:52:07 +02:00
Author
Owner
Copy Link

Completed and merged via PR #93.

Completed and merged via PR #93.
domverse moved this to Done in Photo Analyzer Delivery on 2026-08-17 23:02:17 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/backend
Backend services, jobs, or API
 area/database
Schema, persistence, migration, or queries
 area/filesystem
Filesystem identity, mutation, or storage
 area/frontend
Browser UI and client-side application
 area/integration
External tools or provider integrations
 area/testing
Automated test suites, fixtures, and tooling
 priority/critical
Release-blocking safety or correctness
 priority/high
Important phase outcome
 priority/normal
Normal planned work
 status/backlog
Awaiting dependency eligibility or prioritization
 status/blocked
Cannot proceed without an explicit resolution
 status/done
Merged, tested, and completed
 status/in-progress
Currently being implemented
 status/ready
Eligible to be claimed
 status/review
Submitted in a pull request for review
 type/feature
User-facing or domain capability
 type/hardening
Security, resilience, operations, or release hardening
 type/migration
Donor extraction, migration, or legacy consolidation
 type/test
Automated test infrastructure or acceptance coverage
No Label area/backend area/testing priority/normal status/done type/hardening
Milestone
No items
No Milestone E07 — Hardening and Release
Projects
Clear projects
No project Photo Analyzer Delivery
Assignees
Clear assignees
domverse
No Assignees domverse
1 Participants
Notifications
Due Date
No due date set.
Blocks
#44 US07-07 — Automate Full Release Acceptance
domverse/photoanalyzer
Depends on
#41 US07-04 — Prove Concurrency and Crash Recovery
domverse/photoanalyzer
#42 US07-05 — Deliver Backup and Operational Recovery
domverse/photoanalyzer
Reference: domverse/photoanalyzer#43
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?