Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10, while SingleStore 9.0 is recommended for production workloads.

PROFILE PIPELINE

On this page

Note

PROFILE PIPELINE command has been deprecated from SingleStore versions 9.0 and later. SingleStore recommends using the SHOW PROFILE PIPELINE command instead.

The PROFILE PIPELINE command runs a single batch in the foreground to provide detailed resource metrics for each operation in your pipeline. The batch itself is not persisted.

Syntax

PROFILE PIPELINE pipeline_name

Remarks

  • This command causes implicit commits. Refer to COMMIT for more information.

  • pipeline_name is the configured pipeline.

  • Refer to the Permissions Matrix for the required permissions.

  • To use PROFILE PIPELINE, you must gather data source offsets through TEST PIPELINE. Verify that TEST PIPELINE does not return an empty set before calling PROFILE PIPELINE.

    See TEST PIPELINE for more details.

Note

You cannot run PROFILE PIPELINE when the pipeline is in a Running or Error state.

Example

The output of PROFILE PIPELINE is similar to the SHOW PROFILE output described in PROFILE.

Example

TEST PIPELINE kafka LIMIT 10;
+---------+
| id      |
+---------+
| rlkj    |
| slkjrl  |
| sdlkj   |
| sk      |
| slkjrls |
| lkjrljs |
| slkjr   |
+---------+
PROFILE PIPELINE kafka;
+------------------------------------------------------------------------------------------------------------------------------------------------------+
| PROFILE                                                                                                                                              |
+------------------------------------------------------------------------------------------------------------------------------------------------------+
| Gather partitions:all est_rows:264 alias:remote_0 actual_rows: 7 exec_time: 0ms                                                                      |
| InsertInto quickstart_kafka.messages [messages_src.id] local:yes est_rows:264 actual_rows: 7 exec_time: 0ms start_time: [00:00:00.259, 00:00:00.280] |
| ExternalIngest pipeline:kafka                                                                                                                        |
| |---CSVParse actual_rows: 7 exec_time: 0ms start_time: [00:00:00.005, 00:00:00.030] end_time: [00:00:00.259, 00:00:00.280]                           |
| |---Transform streamed_bytes: 0.043000 KB exec_time: 4ms start_time: [00:00:00.005, 00:00:00.030] end_time: [00:00:00.259, 00:00:00.280]             |
| +---Extract streamed_bytes: 0.092000 KB exec_time: 269ms start_time: [00:00:00.005, 00:00:00.030] end_time: [00:00:00.256, 00:00:00.278]             |
+------------------------------------------------------------------------------------------------------------------------------------------------------+

Last modified:

Was this article helpful?

On this page

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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In