OpenParable
Skip to content
← Back to skills

Performance Streaming

Development
performance-streaming

Performance Streaming is an Agent Skill for development published in the fossasia/visdom repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Optimize high-throughput visualization updates across server broadcast and frontend batching paths

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/fossasia/visdom/blob/HEAD/.agents/skills/performance-streaming/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/performance-streaming, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Skill: Performance for Streaming Updates

When to Use

Use this skill when large update volume causes lag, dropped frames, or heavy CPU/network use.

Core Workflow

  1. Profile payload size and update frequency from Python client sends.
  2. Prefer incremental updates/patches over full pane re-send.
  3. Keep server broadcast fanout minimal and environment-scoped.
  4. Preserve frontend batching/coalescing behavior for incoming pane updates.
  5. Avoid unnecessary pane re-renders by preserving pane identity and memoization assumptions.

Guardrails

  • Do not trade correctness for speed in patch generation.
  • Keep compare mode and normal mode both stable under load.
  • Validate behavior in both WebSocket and polling modes.

Documentation

  • Skill reference
  • py/visdom/utils/server_utils.py
  • py/visdom/server/handlers/socket_handlers.py
  • js/main.js
  • js/api/ApiProvider.js
  • AGENTS.md
  • CONTRIBUTING.md

Assets

  • See assets/README.md and store templates/resources in assets/.

Tests

  • Follow the default flow in references/TESTS.md.