Compare
Filament vs OLake
Side-by-side capabilities and benchmarks.
ROWS PER SECOND
235.7 s
2.0× FASTER
NYC Taxi, MySQL -> Iceberg
CPU SECONDS
16.6 s
15.0× LESS
NYC Taxi, Postgres -> Iceberg
PEAK MEMORY
23.9 s
1.5× LESS
NYC Taxi, MySQL -> Iceberg
WALL TIME
528
1.1× SLOWER
NYC Taxi, Postgres -> Iceberg
OLake is an open-source tool for replicating databases into a lakehouse. It reads from databases and writes to Apache Iceberg or Parquet. It is focused on that one path and does it well. Filament is an open-source replication engine that writes Iceberg too, alongside Postgres, MySQL, ClickHouse, and S3, from one binary.
Verified benchmark comparison
Why Filament
Apache 2.0, open source
Self-hosted in full
Yes. One repository, no paid tier, nothing gated
Adding a new source
A YAML manifest for REST APIs, loaded at runtime with no rebuild. A Go driver for databases and other driver-based sources
Methodology
Configuration as run. Filament standalone image, 32 parallel readers, 25,000-row batches. OLake latest source-postgres and source-mysql images, Arrow writes on, 32 threads, full refresh. On the one scenario OLake won, it held 39 of the host's 64 cores busy for the whole run. Filament held 2.3. Swap the source from Postgres to MySQL on the same 298M rows and OLake more than doubles its time while Filament moves by 1.4 seconds.
Move data with Filament