Sign inTry Free

Scale a Instance

On this page

Flow on Helios instances can be resized after creation to match workload requirements and control credit consumption. Instance sizing is based on Flow instance size tiers (F1 - F3), each with a defined vCPU, memory, and credit rate per hour.

When selecting a new size, consider the following:

  • vCPU ratio to workspace: Choose a Flow instance size so that Flow vCPUs are approximately one quarter of the vCPUs in the destination workspace (a 1 : 4 Flow-to-workspace vCPU ratio). This generally provides good performance balance between ingestion and query workloads.

  • Workload characteristics: If the size and characteristics of the data are already well understood (data volume, number of tables, largest table size, expected concurrency, and required completion time), adjust the instance size accordingly to better fit the workload.

For detailed sizing guidance by workload type, including example scenarios and recommended sizes, refer to Flow on Helios Sizing Guidelines.

Flow Instance Sizes

The following table lists the available Flow instance sizes and their resources:

Size

vCPU

Memory

Credits per Hour (CR)

F1

2

4 GB

0.123 CR

F2

4

8 GB

0.246 CR

F3

8

16 GB

0.492 CR

F4

16

32 GB

1.084 CR

F5

32

64 GB

2.069 CR

F6

64

128 GB

4.138 CR

F7

96

384 GB

9.643 CR

F8

192

768 GB

18.731 CR

Depending on environment and preview configuration, higher tiers (for example, F4 and above) may appear disabled in the dialog. In that case, only the enabled sizes are available for selection.

Scale a Flow Instance in the Cloud Portal

To change the size of an existing Flow on Helios instance:

  1. In the Cloud Portal, navigate to Load Data > Flow.

  2. In the Actions column for the instance to scale, click the three dots (…) and select Scale.

  3. In the Scale Flow Instance dialog:

    1. Review the recommendation text and confirm the target size based on the destination workspace vCPUs and workload characteristics.

    2. Select the desired Flow instance size from the Size column.

    3. Review the associated vCPU, Memory, and Credits Per Hour values.

    4. Save the change in the dialog to apply the new instance size.

After the change is applied, the Flow instance runs with the newly selected size, and subsequent usage is billed at the corresponding credit rate. For more information on how instance size affects cost, refer to Helios Pricing.

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