mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-11 14:00:29 +00:00
rcourtman
054ef7de13
The 2026-08-25 evening perf pass re-profiled the remaining frontend costs on the 50-node mock rig afterd5440ff43. Idle main-thread burn on a throttled phone (~10.5s of long tasks per 30s on the worst-case mock) and residual warm tab-entry cost both decomposed into per-changed-row work that ignores what actually changed: every metrics tick deep-cloned, re-canonicalized, and fully re-merged each patched row, and both store commits then deep-unwrapped the merged rows again through whole-row keyed reconciles. The server's resource delta is a JSON merge patch, so the change shape is already known. applyResourceStateDelta now records the top-level keys each patch touched (platformData expanded one level), the connection store publishes them with the resource revision and unions them across the bounded history and the hidden-tab deferral set, and mergeCanonicalResourceDeltaSnapshot takes a fast path for changed non-host rows whose keys stay within the pass-through metric fields, the proxmox facet mirror, and the four platformData metric mirror leaves: the previous display row with just those subtrees cloned in (a manual plain-data clone — structuredClone's per-invocation setup dominates at this size). Both commit sites write fast rows as per-key subtree patches (nested reconcile for records, direct sets for primitives and platformData leaves) instead of whole-row reconciles, and the connection store commits aligned ticks per index. Any other change shape — additions, removals, repeated patches in one frame, structural keys, agent rows (host coalescing) — keeps the full clone-canonicalize-merge path, and the fast output is pinned content-equivalent to it in resourceStateAdapters tests; a websocket store test pins the per-key change shapes, the meta-history union, and its unknown-shape contamination. Measured on the pulse-dev rig (VM-to-VM, 50-node/1500-resource mock, worst-case RandomMetrics, vs twod5440ff43baseline runs): mobile-4x idle long tasks 10.8/10.2s -> 3.9s per 30s; warm Alerts entry 5-rep median long-task total 3.85s -> 1.52s; mobile warm Overview return 3.8/1.7s -> 1.0s; desktop Backups entry settle 1.06/1.20s -> 0.71s; warm Storage/Overview sub-tab switch medians flat within rep spread; desktop cold load and /api/state size unchanged. Browser-verified on the rig build of this tree: live ticks render through the fast path with per-cell DOM-vs-store consistency at two samples 30s apart, zero console errors, desktop and 390px/4x mobile.
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.