SelanjutnyaPanduan berikutnya
Docker Containers for ML Models
Teknis
PANDUAN Teknis
A two-tower recommender encodes a user or query and each candidate item separately into vectors, then scores a pair by vector similarity.
Because item vectors can be precomputed and indexed, two-tower models support scalable retrieval before a more detailed ranking stage.
Recommendation systems often separate candidate retrieval from ranking. Retrieval narrows a large catalog to a manageable set of potentially relevant items. A two-tower model uses one encoder for the user or query and another for candidate items. Each tower transforms its own available features into a vector in a shared embedding space. A similarity function, often a dot product or cosine score, ranks candidate pairs. The two encoders can be run independently. Item embeddings may be calculated offline and stored in a nearest-neighbor index. At request time, the user tower creates a query vector and the index returns a shortlist. This separation supports large catalogs more efficiently than evaluating a deep joint model against every item. TensorFlow Recommenders describes this architecture as retrieval with query and candidate models. The independent structure creates a tradeoff. It scales retrieval, but it cannot directly model arbitrary pairwise interactions that require seeing the user and item together, unless those interactions are represented in the embedding training objective or features. A downstream ranker can combine retrieved candidates with richer context, cross-features and operational constraints. Retrieval recall matters: a ranker cannot select an item that was never retrieved. Training often uses positive interactions and sampled or in-batch negatives to shape the embedding space. The negative sampling strategy and exposure logs affect what the model learns. Evaluation should measure recall or ranking among a realistic candidate pool and check cold-start performance. Monitor embedding freshness, index refreshes and feature-version compatibility. A high similarity is a retrieval score, not a calibrated probability or proof of user preference. Eligibility, safety, diversity and policy constraints should be applied in the system design. The architecture makes large-scale search practical, while final user experience depends on candidate coverage, ranking quality and evaluation beyond offline similarity.
Keputusan arsitektur mendorong kinerja dan biaya pengoperasian selama bertahun-tahun.
Pendidikan teknis membantu tim memilih tumpukan yang tepat, bukan hanya yang terbaru.
Pilihan teknik yang lebih baik mengurangi insiden keandalan dalam produksi.
Two-tower systems can become more useful by monitoring candidate recall, embedding freshness and latency alongside final ranking outcomes. Teams should version towers and indexes together and test feature changes before rebuilding retrieval infrastructure. As user and item populations grow, approximate search can improve scale but should be checked against exact retrieval on samples. A separate ranker can add context while preserving a clear retrieval stage. Reports should explain that similarity produces candidates, then show how later filters and ranking influence what users actually see.
A hypothetical music app encodes a listener's recent activity into a user vector and each song's metadata into an item vector. A nearest-neighbor search retrieves songs whose vectors are similar.
A retrieval service precomputes item embeddings and searches them with an approximate nearest-neighbor index, avoiding a full neural-network evaluation for every user-item pair at request time.
A ranking model then considers additional pair-specific context such as current session, freshness and business constraints, which separate towers may not capture during retrieval.
A team checks that user and item embeddings are generated from compatible versions and dimensions; mismatched preprocessing or stale item vectors can degrade similarity scores.
Mengoptimalkan satu tolok ukur dapat menyembunyikan kelemahan sistem yang lebih luas.
Biaya infrastruktur dan pemeliharaan sering kali diremehkan.
Kesenjangan keamanan dan kemampuan observasi dapat tumbuh seiring dengan semakin kompleksnya sistem.
Tentukan target latensi, kualitas, dan biaya sebelum penerapan.
Tolok ukur dalam kondisi beban dan data yang realistis.
Pemantauan instrumen untuk kesalahan, penyimpangan, dan dampak pengguna.
Siapkan jalur rollback dan respons insiden sebelum melakukan penskalaan.
Free newsletter
Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.
One email each weekday. Unsubscribe in one click. We never sell or share your address.
Test yourself
Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.
Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation
A two-tower recommender encodes a user or query and each candidate item separately into vectors, then scores a pair by vector similarity. Because item vectors can be precomputed and indexed, two-tower models support scalable retrieval before a more detailed ranking stage.
Kedua pembuat enkode secara independen memetakan fitur sisi kueri dan sisi kandidat ke dalam ruang vektor bersama.
Karena vektor item dihitung secara independen, vektor item dapat dibuat secara offline dan diindeks.
Indeks vektor mendukung pencarian kesamaan pada penyematan item yang telah dihitung sebelumnya.
Pemeringkat hilir hanya melihat kandidat dikembalikan melalui pengambilan, sehingga kandidat yang terlewat tidak dapat dipulihkan di sana.
Pengkodean independen lebih menyukai skala tetapi mungkin tidak menangkap interaksi kaya yang memerlukan kedua belah pihak secara bersama-sama.
Teruslah belajar
Panduan lainnya dipilih untuk topik ini
SelanjutnyaPanduan berikutnya
Docker Containers for ML Models
Teknis