📝 Record full annotation optimization acceptance and scrub test credentials

This commit is contained in:
eust-w 2026-09-17 19:55:53 +08:00
parent 5498892cda
commit 03d1893101
2 changed files with 30 additions and 0 deletions

View File

@ -29,3 +29,29 @@ No change to dictionary selection, role/supplier ownership, semantic blanks, exp
## Verification
Focused tests cover durable outbox BSON/JSON privacy, concurrent exclusive claims, expired-owner fencing, process replacement, source changes, persistent index recovery/corruption, proactive indexing, semantic-empty submission, metadata-only generation, decoded frame equivalence and delivery ownership/retry behavior. Live load tests must use a separate database/processor and private Run prefixes; production source objects are read-only. Report the tested concurrency and actual video duration rather than extrapolating unlimited capacity.
## Fanyu verification — 2026-09-17
Deployed implementation: `b57980fd`. API and independent annotation processor use API digest `sha256:886d7ed7d4f53180243d780bc5a95b241babfd703357e9507b0c2d4db70792dc`; Worker digest `sha256:8c3897e1a77ca173c341ff8dee838abe10925596d7b1fc6b73479e6d04f7ec8b`. API mode is `external`, processor concurrency is two. Algorithm and package operator images remain unchanged.
Load validation used five separate accounts and five independent tasks referencing the same real 842.966667-second source Capture. It used a separate database and API/processor deployments in Fanyu, not production staff tasks. This measures a five-client repeated-sample workload, not arbitrary fleet capacity.
| Operation | Median | P95 | Samples |
| --- | ---: | ---: | ---: |
| First timeline response after precomputation | 547 ms | 549 ms | 5 |
| Repeated timeline response | 747 ms | 1,492 ms | 50 |
| Confirm slice request accepted | 240 ms | 250 ms | 5 |
| Status read during processing | 72 ms | 128 ms | 50 |
| Save description | 219 ms | 252 ms | 5 |
| Submit description request accepted | 102 ms | 116 ms | 5 |
- Before the compact wire format, the same five-client test still took 10–14 seconds to transfer full timeline responses, despite a fast cached helper. This led to the lossless wire optimization; no server-only timing is reported as browser performance.
- A 27,001-point fixture encoded from 1,736,701 to 15,511 bytes. Go-to-JavaScript and actual Chrome decoding restored every integer and IEEE-754 time exactly; Chrome decode took about 13 ms. No duration/frame resampling was introduced.
- The isolated processor Pod was deleted during active long-video processing. Jobs resumed on the replacement processor, with affected attempts incrementing to two; all five slice tasks and metadata-only submissions completed. The initial comparison run also completed recovery. Sample readback verified 21 files and 50,573 decoded stereo frames against checksums/PTS after each run.
- Long-video generation logs under two active jobs changed from approximately 375–388 seconds per job to about 224 seconds in the optimized input/decoder run. Physical generation is still background work; request-acceptance timings above do not claim that videos are generated in milliseconds.
- Production functional fixture: `project-discard-verify-20260917allqa1`. Mixed/rework/invalid-only/discard path produced child `run-human-release-61c4cb89cece43f47843391dbc7cf868`, 2 delivered slices / 40 seconds / 23 verified files / 320 stereo frames. All-blank path produced `run-human-release-2b386cb57fb91d8dc83e83226b67efbf`, 3 slices / 60 seconds / 30 files / 480 frames / zero invented annotations. Both reached `delivered`; discarded evidence remained available in QA/acceptance but not in delivery.
- Actual production browser submission used summary reads, one compact timeline request, and one lightweight status poll during the measured interaction. It displayed processing after 202 and returned to the pool only on authoritative quality handoff. Role-release prohibitions and dictionary constraints were retested.
- Existing full-suite failures remain unchanged: 60 API tests and 9 frontend tests. The expanded frontend suite has 545 tests, 536 passing. Targeted concurrency/race, persistence, recovery, decoded-frame equality and browser checks passed.
- Performance deployments were removed after the runs; synthetic accounts were disabled. Test data and evidence were retained, but copied sandbox storage credentials were cleared. Original production files were read-only.
Remaining limits: an input whose index is still being prepared can still wait; queues still wait for finite CPU/I/O capacity. Native local filesystem media-copy fallback remains for non-BOS deployments. The measured concurrency was five accounts; higher concurrency needs its own sizing/validation. Chrome was exercised directly; the codec uses standard APIs available in modern Chromium-based Edge, but a separate Windows Edge session was not available for this run.

View File

@ -148,6 +148,10 @@ func TestSeedAnnotationPerformanceSandbox(t *testing.T) {
}
}
fmt.Println("disabled only isolated performance accounts")
_, e = client.Database(name).Collection("storageConnections").UpdateOne(ctx, bson.M{"id": "storage-d0a49fe4b9881c324f0640ab62359603", "organizationId": "org-29cd7a684faba19f630f8ad5890e18bb"}, bson.M{"$unset": bson.M{"accessKeyId": "", "secretAccessKey": ""}})
if e != nil {
t.Fatal("remove copied sandbox credentials")
}
return
}
collections, e := client.Database(name).ListCollectionNames(ctx, bson.M{})