Home / Companies / Tecton / Blog / Post Details
Content Deep Dive

Building a High Performance Embeddings Engine at Tecton

Blog post from Tecton

Post Details
Company
Date Published
Author
Brian Hart
Word Count
1,711
Company Posts That Month
1
Language
English
Hacker News Points
-
Post removed?
No
Summary

Tecton has built a high-performance Embeddings Engine to complement its Aggregation Engine, using PyArrow, PyTorch, and Tokenizers/Transformers. The engine is designed to allow users to quickly and efficiently batch-generate text embeddings with open-source models and use them in production applications. It meets several key requirements, including top-tier performance with minimal configuration, distributed batch model inference on GPU instances, and automatically tuned model inference to leverage available computational resources. The Embeddings Engine is built around Tecton's Rift engine, which supports diverse computational workloads through separate computational stages. The engine implements several performance optimizations, such as single node parallelism using multi-threading, distributed inference, handling larger datasets, optimizing input processing, and fine-tuning batch operations. It also addresses challenges like input length sorting, dynamic token batching, automated token budget selection, CUDA OOM batch splitting, and results in significant improvements in throughput and resource utilization. The engine's performance is auto-tuned to the local hardware, allowing for easy adoption of new OSS models and customer models. Future enhancements include more flexibility, better performance, and further optimizations for batch and real-time generation of embeddings.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Vector Search 25 1,644 222 91 +2%
Real-time 3 2,178 673 199 -6%
AI Model Fine-tuning 1 978 142 70 +21%
RAG 1 1,642 187 75 +52%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.