LogoLogo
Release notesAPI docsDocs homeEphemeral CloudTonic.ai
  • Tonic Ephemeral guide
  • About Tonic Ephemeral
  • Getting started with the Ephemeral free trial
  • Managing your Ephemeral account
  • Managing Databases
    • Viewing the list of databases
    • Starting a database
    • Changing the database configuration
    • Database configuration settings
      • Setting the required resources for a database
      • Setting the database expiration
      • Providing a custom configuration file
    • Connecting to a database
    • Resetting a database
    • Deactivating and reactivating databases
    • Managing auto snapshots
    • Tracking database activity
    • Deleting a database
  • Managing user snapshots
    • About user snapshots
    • Viewing the user snapshot list
    • Creating a user snapshot from an Ephemeral database
    • Creating a user snapshot from imported data
    • Editing a user snapshot
    • Creating a database from a user snapshot
    • Deleting a user snapshot
  • Installing and configuring Ephemeral
    • Ephemeral architecture
    • Configuring an allowlist for Ephemeral Cloud database connections
    • Installing a self-hosted instance of Ephemeral
      • System requirements
      • Deploying Ephemeral with Helm
    • Configuring database access on a self-hosted instance
    • Configuring tolerations and node selectors
    • Managing access to Ephemeral
      • Managing Ephemeral users
      • Enabling SSO on a self-hosted instance
        • Google
        • Okta
    • Setting the registry location for data volumes
    • Managing custom images
      • Creating, editing, and deleting custom images
      • Oracle image configuration
    • Configuring automatic deletion of snapshots
  • Monitoring and data collection
    • Monitoring your Ephemeral billed usage
    • Monitoring your disk storage
    • Data that Tonic.ai collects
  • Using the Ephemeral API
    • About the Ephemeral API
    • Configuring Ephemeral
    • Getting information about Ephemeral databases
    • Starting a database
    • Managing databases
    • Managing snapshots
Powered by GitBook
On this page
  • Disk space allocation
  • Compute resources

Was this helpful?

Export as PDF
  1. Managing Databases
  2. Database configuration settings

Setting the required resources for a database

PreviousDatabase configuration settingsNextSetting the database expiration

Last updated 1 year ago

Was this helpful?

For a Tonic Ephemeral database, you can specify disk space and compute resources. After you set these values for a database, you cannot change them.

Disk space allocation

In the Disk space allocation field, specify the size in gigabytes to allocate to the database and to each of its snapshots. For a free trial, a database cannot use more than 100 GB.

Ephemeral uses that value to calculate the amount of space being used by the current databases and snapshots, and to determine the amount of disk space that can be used before Ephemeral displays a warning. For information about how to monitor disk space usage and configure the alert threshold, go to Monitoring your disk storage.

Compute resources

From the Compute resources dropdown list, select the option to use for the combination of vCPUs and memory:

  • Nano - 0.125 vCPU with 0.5 GB RAM

  • Micro - 0.5 vCPU with 2 GB RAM

  • Small - 1 vCPU with 4 GB RAM

  • Medium - 2 vCPU with 8 GB RAM

  • Large - 4 vCPU with 16 GB RAM

Settings for disk space allocation and compute resources