mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-10 18:45:53 +00:00
rcourtman
c154fa7aed
Wheel scrolling the Proxmox overview on a 929-guest estate hitched for 200-260ms per runway rebalance. Four compounding causes, all fixed: - The windowing runway policy rebalanced in ~53-row jumps inside a non-passive wheel listener, so the compositor waited on a multi-frame remount. Both windowing owners now keep a symmetric runway topped up in dead-band batches (one bounded mutation frame per ~8 rows of travel), every windowed-page listener is passive, and only a viewport that leaves the mounted window entirely re-centers it in one jump. - The Workloads viewport-sync effect tracked the windowing signals its own measurement pass moves, so every shift re-ran row measurement (two forced reflows) and listener binding. The measurement pass is now untracked, matching the unified-resource sync owner; the platform and storage windowing owners had the same latent tracking and are untracked too. - WorkloadPanel built its guest-id lookup from the windowed slice, so a shift re-validated every mounted row's memo chain. The lookup now derives from the full group and only changes when data changes. - The CPU/memory/disk bar hooks read offsetWidth in onMount, forcing a full-table reflow per mounted bar during every top-up. Width now comes solely from the ResizeObserver's initial pre-paint delivery. Prewarmed-but-hidden platform tabs also ran viewport sync per scroll event and paid the visible surface's layout flush; hidden surfaces now skip sync via a shared checkVisibility guard. Measured on the 50-node/929-guest mock estate at 2560x1240: a 4-row top-up fell from ~230ms to ~7ms, scroll-jitter oscillation produces zero frames over 25ms, and sustained fast scrolling holds native frame cadence with one bounded mutation frame per dead-band. The remaining scroll-time long tasks are realtime websocket merge ticks, which the realtime-merge lane already owns.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.