Search the bucket
Loading object storage into both a search cluster and a warehouse creates three copies of the same rows. Infino searches the copy in your bucket.
The index lives inside the file
- Both indexes, keyword and vector, live inside the Parquet file next to the columns they index.
- The engine reads byte ranges from the bucket and caches the hot parts locally.
- The same files remain standard Parquet.
- Search and SQL pin the same snapshot, so both paths resolve the same active rows.
Measured warm latency
Per-file summaries in the manifest prune files that cannot match before a byte is read, and workers cache the hot byte ranges on local disk. In an internal run over 10M documents, warm full-text p50 is 2 ms. Warm vector top-10 is 5 ms at p50 and 12 ms at p99. The published runs, each with a way to reproduce it, are on the search latency benchmark page.
How the engine is put together → · Opening a file on S3 used to take two round trips →
Keep one copy, in your own bucket.
Free tier · No credit card to start
or run it yourself: pip install infino · Apache-2.0 · quickstart →
Next: what hybrid search is · the query surface · back to hybrid search