ask about this project

Aperta
#191 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
20/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
kubernetes, python, rust

Direzione di ricerca

This issue asks broad questions about SIE's architecture, model catalog, deployment, performance, API compatibility, and roadmap; it does not name files or tests to start from. Read the project documentation and existing discussions, then check whether a maintainer has responded to the questions. Done means providing answers grounded in the project's current behavior and plans.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

SIE unifies embeddings, reranking, and extraction under one API with on-demand loading + LRU eviction. What were the biggest technical challenges in supporting such a diverse set of architectures (dense, sparse, multi-vector, ColBERT, vision, cross-encoders, GLiNER, etc.) in a single Rust/Python backend?
How do you handle model compatibility and quality verification? You mentioned MTEB CI checks — what’s your process for adding new models, and how often do you update the 85+ model catalog?
Memory management: What’s the practical limit for running multiple large models simultaneously on a single GPU (e.g., 24GB or 80GB)? Any clever optimizations for mixed precision, quantization, or batching?
In production (Kubernetes with KEDA autoscaling), what kind of latency and throughput do you typically see for common models like BGE, Stella, or BGE-reranker on GPU vs CPU?
Compared to alternatives like vLLM, TGI, Ollama, or dedicated embedding servers (e.g., TEI), what are the biggest advantages and trade-offs of SIE?
OpenAI-compatible /v1/embeddings endpoint is great for migration. How complete is the compatibility, and do you plan to expand it (e.g., reranking or extraction endpoints)?

If someone wants to add custom models or new task types (e.g., more advanced extraction, OCR, or multimodal), what’s the best way to extend SIE while keeping it within the unified API?
Plans for the roadmap: Any support for fine-tuned models, LoRA adapters, continuous batching, or more advanced routing strategies?
The project mixes Rust (core performance) and Python. How do you manage the boundary, and any lessons learned from that hybrid approach?

Lingua principale
Python
Stelle
3.5k
Fork
328
Merge medio
16h 25m
PR unite (30g)
121

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di superlinked/sie

Tutte le issue di superlinked/sie

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.