Segmented Sieve (HTTP) Control Panel

Role: This page controls the Segmented Sieve of Eratosthenes (SSPrime) distributed prime computation lane. Compute runs in browser worker tabs leasing segment ranges over HTTP.

SSPrime Run Controls & Operator Block: The page features both legacy buttons (Start New SSP Run, Stop SSP Run, Pause SSP Run, Resume SSP Run in the collapsible details) and the primary Operator block (#wo6-ssp-*) below: Reload Config (loads active configuration from the server), Stage Config (stages form parameters in memory), Save as Default (persists configuration as server boot default), Reset Staged Changes (discards pending staged edits), Stage & Start New Run (stages parameters and starts a new run immediately), Start New Run (starts an SSPrime computation run), Pause Run (halts issuing new segment leases), Resume Run (resumes issuing segment leases), Stop Run (stops the active run), Restart Run (restarts the run with active configuration under a new run ID), Refresh Now (re-reads server state), Archive & Clear Previous Run Data (archives run state and event log to archive/ssprime/<timestamp>/ and resets to idle), Restart Server (restarts the pool_admin service; note: this temporarily affects both SSPrime and Matrix).

Configuration States: SAVED DEFAULT is loaded by the server at boot; ACTIVE is what the current run uses; STAGED NEXT-RUN holds in-memory parameters that take effect on the next Start or Restart Run.

Events & Log Links: Diagnostic and verification links include the in-page Client Worker Log, Live Worker Logs (/LogWorkerTaskProgressData.html), SSP Event Logs (/ssp_event_logs.html), and the Task Summary Panel (#wp4-task-summary), which tracks summaries per segment lease and lease batch.

Shared Persistence Panel: The unified persistence panel (mounted via persistence_panel.js) provides live monitoring of coordinator storage health, active keys, and checkpoint intervals.

Glossary:

• Lane: Computational track (SSPrime computes prime segments via HTTP leasing).
• Device ID vs Tab ID: Device ID persists per browser profile in localStorage; Tab ID names an individual ephemeral worker tab connection.
• Liveness TTL vs Task Lease: Liveness TTL renews pool presence via heartbeat; task lease represents an assigned segment range with a timed deadline.
• Batch: Number of segments leased in a single HTTP request (batchK / maxWant).
• Stage: Holding candidate parameter changes in memory until the next run start or restart.
• Restore: Restoring prime progress and segment counters from disk archives or checkpoint snapshots.
• Purge: Removing an idle or disconnected worker tab after a server-side countdown.
• Affinity / Strict: Cluster targeting for worker assignments.
• Checkpoint Mode: Persistence strategy for saving run state to durable storage.