Pain Point

Performance-per-Dollar

The composite metric that evaluates S3-based data system efficiency by normalizing query throughput, scan latency, or ingestion rate against total cost (storage, requests, compute, egress, and caching), enabling apples-to-apples comparison of architectural choices.

3 connections 3 resources

Summary

What it is

The composite metric that evaluates S3-based data system efficiency by normalizing query throughput, scan latency, or ingestion rate against total cost (storage, requests, compute, egress, and caching), enabling apples-to-apples comparison of architectural choices.

Where it fits

Performance-per-dollar is the ultimate evaluation criterion for S3-based architecture decisions. Choosing between Parquet and ORC, Iceberg and Delta, Trino and Spark, or AWS S3 and MinIO should be grounded in measured performance-per-dollar, not raw performance alone.

Misconceptions / Traps
  • Raw performance benchmarks (queries per second, scan throughput) are meaningless without cost context. A system that is 2x faster but 5x more expensive is not a better choice.
  • Cost in S3-based systems has many components: storage per GB, request pricing, compute (spot vs on-demand), egress, and metadata API calls. Benchmarks that omit any component are misleading.
  • Performance-per-dollar changes with scale. A system that is cost-efficient at 1 TB may be uneconomical at 1 PB due to metadata overhead, request amplification, or catalog limits.
Key Connections
  • scoped_to S3, Lakehouse — cost efficiency across S3-based systems
  • depends_on Benchmarking Methodology — measured by controlled benchmarks
  • constrains Request Pricing Models — request costs are a key component
  • constrains Egress Cost — egress is a significant cost factor in multi-region designs

Definition

What it is

The metric of query throughput, latency, or processing speed normalized to total cost (storage + compute + API calls + egress) for S3-based data systems, used to compare architectures, engines, and storage configurations.

Connections 3

Outbound 2
Inbound 1

Resources 3