Skip to content

Deterministic IPTV corpus and performance benchmarks #27

Description

@MrFr3di

Objective

Maintain the repository-owned deterministic IPTV measurement authority used to justify parser, database, UI and playback optimizations. Correctness/compatibility fixtures are owned separately by #186; this issue owns scale/performance evidence and provenance.

Current execution checkpoint

Canonical virtual-device contract

Repository-owned Android correctness/measurement execution uses only:

  • MuxTV_TV_OLD_API26;
  • MuxTV_TV_CURRENT_API36.

There is no third low-RAM, benchmark, catalog, player, variance, 720p or representative-mainstream AVD. Low-memory/display/stress conditions are configurations/evidence dimensions of the two canonical devices where the platform allows it.

Emulator measurements validate repeatability/correctness and relative changes on the named environment. They do not establish weak-ARM/vendor MediaCodec/HDR/passthrough/thermal/absolute-TV-performance claims; those require physical-device evidence through #31.

Measurement families

Ingest / source refresh

Database

Only after #178:

UI

  • startup/frame p50/p95/p99 and jank for accepted CUJs;
  • D-pad action-to-visible-result latency where causal measurement is feasible;
  • Compose stability/recomposition evidence only when used for an actual decision.

Playback

Evidence infrastructure relationship

Methodology

  • compare like-for-like environment/corpus/commit provenance;
  • report distributions, not one-off timings;
  • initial measurements are descriptive until repeated variance evidence supports a threshold;
  • timed 50k work remains manual stress evidence rather than a mandatory PR/release gate unless separately promoted with data;
  • do not optimize a component solely from static inspection when a measurement can falsify the hypothesis.

Acceptance

  • deterministic corpus/profile seed remains reproducible;
  • every report records exact source commit + environment metadata;
  • same comparison uses the same corpus/profile and equivalent device/runtime configuration where practical;
  • no structural/runtime optimization is accepted from a stale or known-invalid measurement boundary;
  • fix(measurements): align search boundary evidence with published results #178 is accepted before DB-query conclusions are used;
  • no performance claim generalizes emulator evidence to physical weak TVs;
  • no additional AVD identity is created.

Non-goals

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions