41.8 GB/sec. 133.5 million rows/sec. One native Snowflake table. Our synthetic Snowpipe Streaming benchmark in AWS us-west-2 sustained 41.8 GB/sec of uncompressed throughput with Elastic Channels. Throughput grew linearly as we scaled from 15 to 455 Kubernetes workers. The setup combined Elastic Channels, 1-vCPU worker pods and Rust-based encoding to reduce client-side overhead. Building telemetry or log pipelines? See the benchmark method, latency measurements and how to start with one worker:

A 2,500 GB database with a 20 GB hot working set doesn’t need 2,500 GB of RAM. That principle runs through Lakebase Postgres cost optimization: size around what your application actually needs. ✦ Sync only the working set your app queries ✦ Match Snapshot, Triggered or Continuous sync to freshness requirements ✦ Size compute so hot data fits in cache ✦ Set PITR and snapshots around actual recovery needs The full guide breaks down how to keep costs predictable while maintaining the performance, availability and developer experience applications need: