Livestream: Ducklake & The Future of Open Table Formats - June 17Register Now

Skip to main content

Instance Types

MotherDuck implements a distinct tenancy architecture that diverges from traditional database systems. The platform utilizes a per-user tenancy model, which provisions isolated read-write instances for each Organization member. This architecture ensures dedicated compute resources and instance-level configuration at the individual user level, allowing users to independently optimize performance parameters according to their specific workload requirements. Each instance type has different performance characteristics and billing implications. MotherDuck uses fast SSDs for spill space, so queries can exceed their memory limits with minimal performance impact. DuckDB caches data in memory, and MotherDuck uses fast local disks for storage, which improves cold start times.

Instance Types​

MotherDuck offers several instance types, known as Ducklings, each tailored for different workloads. Choosing the right instance can optimize both performance and cost.

PULSE​

Optimized for ad-hoc analytics and read-only workloads

Pulse instances are auto-scaling and designed for efficiency, making them ideal for:

  • Running ad-hoc queries (Note complex queries involving spatial analysis or regex-like functions may perform better on larger instance sizes)
  • Read-optimized workflows with high concurrent user access, such as those in customer-facing analytics.
  • Powering data apps and embedded analytics where quick, short queries are common.
  • High-concurrency, read-optimized workflows

Learn how Pulse instances are billed.

STANDARD​

Production-grade instance designed for analytical processing and reporting

Standard instances offer a balance of resources for consistent performance, suited for:

  • Core analytical workflows requiring balanced performance metrics.
  • Development and validation environments for production workflows.
  • Standard ETL/ELT pipeline implementation, including:
    • Parallel execution of incremental ingestion jobs.
    • Multi-threaded transformation processing.

Learn how Standard instances are billed.

JUMBO​

Our largest instance built for high-throughput processing

Jumbo instances provide the most resources for demanding tasks, perfect for:

  • Large-scale batch processing and ingestion operations.
  • Complex query execution on high-volume datasets.
  • Advanced join operations and aggregations.
  • RAM-intensive processing of deeply-nested JSON structures or other large data objects.

Learn how Jumbo instances are billed.