SHOW DISTRIBUTED_PLANCACHE STATUS

Note

This feature is an opt-in preview.

Opt-in previews allow you to evaluate and provide feedback on new and upcoming features prior to their general availability.

Provides information about the status and performance of the Distributed Plancache.

This command provides statistics for the node on which it is run.

The following table describes the metrics returned by the SHOW DISTRIBUTED_PLANCACHE STATUS command.

Metric(s)

Description

Successful Downloads Since Startup 

Skipped Downloads Since Startup 

Failed Downloads Since Startup

The number of successful, skipped, and failed plan downloads from the DPC to the local PPC since startup.

Plans Uploaded Since Startup

The number of plans uploaded from the local PPC to the DPC since the startup.

Plans Deleted Since Startup

The number of plans the node has deleted from the DPC since startup.

DB Synchronizations Since Startup

The number of synchronization tasks (manual or automated) that this node has performed since startup.

Successful Downloads From Periodic Sync Since Startup 

Skipped Downloads From Periodic Sync Since Startup 

Failed Downloads From Periodic Sync Since Startup

The number of successful, skipped, and failed downloads that occurred during the periodic aggregator synchronizations since startup.

Applicable to aggregator nodes only.

Periodic Query Plan Syncs Since Startup

The number of periodic aggregator synchronizations since startup.

Applicable to aggregator nodes only.

Distributed Plancache Plans Used Since Startup

The number of plans loaded into memory from the PPC, which originated from the DPC. Tracks how effective the DPC has been in saving re-compilations.

Currently Queued Populate Download Tasks

Currently Queued Download Tasks

Currently Queued Upload Tasks

Currently Queued Delete Tasks

These metrics indicate the number of tasks queued in the DPC task queue.

Avg Plan Download Latency (ms) 

Avg Plan Upload Latency (ms) 

Avg Plan Delete Latency (ms)

The average latency (in milliseconds) from cloud storage.

Avg Duration For DB Plan Synchronization (ms)

Indicates the average length of a synchronization task.

Sample output of the SHOW DISTRIBUTED_PLANCACHE STATUS command:

SHOW DISTRIBUTED_PLANCACHE STATUS;
+-------------------------------------------------------+-------+
| Stat                                                  | Value |
+-------------------------------------------------------+-------+
| Successful Downloads Since Startup                    |  2341 |
| Skipped Downloads Since Startup                       |    45 |
| Failed Downloads Since Startup                        |    12 |
| Plans Uploaded Since Startup                          |   112 |
| Plans Deleted Since Startup                           |    65 |
| DB Synchronizations Since Startup                     |     7 |
| Successful Downloads From Periodic Sync Since Startup |    12 | 
| Skipped Downloads From Periodic Sync Since Startup    |   107 | 
| Failed Downloads From Periodic Sync Since Startup     |     0 | 
| Periodic Query Plan Syncs Since Startup               |     1 | 
| Distributed Plancache Plans Used Since Startup        |    90 |
| Currently Queued Populate Download Tasks              |     2 |
| Currently Queued Download Tasks                       |     6 |
| Currently Queued Upload Tasks                         |    33 |
| Currently Queued Delete Tasks                         |    23 |
| Avg Plan Download Latency (ms)                        |    55 |
| Avg Plan Upload Latency (ms)                          |    33 |
| Avg Plan Delete Latency (ms)                          |    43 |
| Avg Duration For DB Plan Synchronization (ms)         | 11231 |
+-------------------------------------------------------+-------+

Last modified: June 24, 2025

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK