Jessibuca

Performance & Compatibility

Browser and Platform Compatibility

  • Mainstream support across Chrome, Edge, Firefox, Safari, desktop and mobile.
  • Feature-level differences remain for H.265 hardware decode, SIMD, and WebCodecs.
  • Safari generally has different SIMD/H.265 behavior than Chromium-based browsers.
  • WebRTC H.265 support depends on browser + OS + hardware + server path together.

Decode Path Selection Strategy

  1. Prefer hardware decode path when available (MSE/WebCodecs).
  2. Fallback to SIMD software decode where supported.
  3. Fallback to baseline WASM software decode for maximum compatibility.
  4. Apply mode-specific buffering and retry strategies by network quality.

Resolution and Throughput Planning

  • 1080P and above strongly benefit from multithread/SIMD or hardware decode paths.
  • 2K/4K scenarios are heavily hardware and bandwidth dependent.
  • Concurrency planning should include decode mode, GPU limits, and memory headroom.
  • For large concurrency, CDN + multi-tier distribution is recommended.

Bitrate Guidance (Rule of Thumb)

  • 720P: ~1.5–4 Mbps depending on quality target.
  • 1080P: ~4–8 Mbps depending on scene and required detail level.
  • 2K: ~6–12 Mbps for standard/high quality streaming.
  • 4K: ~12–40 Mbps depending on FPS and quality goals.

Final production values should be validated against real device profiles, target concurrency, and observed network jitter/loss characteristics.

Operational Recommendations

  • Profile browser GPU capabilities (for example via browser GPU diagnostics pages).
  • Keep fallback decode modes enabled to avoid hard failure in mixed environments.
  • Monitor first-frame latency, drift, and retry rates as primary runtime KPIs.
  • Use differentiated presets for desktop, Android, and iOS traffic segments.