Keep provider connections alive: TLS handshake costs 4.2s and is paid twice per dictation

Aperta
  • Qualcosa non va?
#998 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
rust
Ambito
networking, performance

Direzione di ricerca

No files are named; start by finding where the provider HTTP client is built for each transcription/polishing request and for the LLM channel-health check (likely a client constructed per call). Confirm connections are torn down after each dictation. Done means a pooled client with a multi-minute idle timeout, a warm-up at startup and on provider/model change, and a configurable request timeout — the issue's 4.2s cold vs 0.18s warm timings are the acceptance signal.

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

Descrizione

Summary

On networks where the TLS handshake to the provider is slow, every dictation pays the handshake
cost twice — once for transcription and once for LLM polishing — because connections are not
kept alive between dictations. On this machine that is the single largest latency term.

Measurements (Windows 11, OpenLess 1.3.18, BYOK OpenAI)

Two requests in a row, the second reusing the connection:

request 1: tcp connect 0.125s | TLS handshake 4.194s | total 4.410s
request 2: tcp connect 0.000s | TLS handshake 0.000s | total 0.183s

The TLS handshake alone costs ~4.2 s; a reused connection answers in 0.18 s, 24x faster.

Supporting numbers:

  • DNS resolution is fine: 259-369 ms, same as any other host. Not the bottleneck.
  • TCP connect is fine: 0.125 s.
  • chatgpt.com behaves identically (~4.1 s on first hit). The ChatGPT website feels instant only
    because the browser keeps one connection open for the whole session.
  • Upload is not the bottleneck: 300 KB takes 2.3 s warm vs 5.4 s cold. The delta is the handshake.

This looks like SNI-based traffic inspection on the ISP side. It is outside the control of the app,
but the app decides how often that cost is paid.

What it looks like in the app

Avg per segment on this machine showed 9.5 s; individual dictations 3.1-5.7 s. The channel
health check for the LLM provider reported 5292 ms. Local ASR was tried as well (Foundry Local and
sherpa-onnx, several Whisper sizes), but with a cloud provider the handshake cost is paid on every
dictation and dominates everything else.

Requests
  1. Keep provider connections alive between dictations — a connection pool with a multi-minute
    idle timeout instead of closing after each request.
  2. Warm up the connection when the app starts, and after the provider or model is changed,
    so the handshake is paid once per session instead of before each dictation.
  3. If a request timeout exists, make it configurable. With a 4 s handshake plus a long
    recording, a fixed short limit produces confusing timeout errors.
Why this is worth doing

For users behind traffic inspection this term is larger than model choice or prompt size.
Two connection settings would cut several seconds off every dictation without changing any
product behaviour.

Related: #994 (plain-text insertion mode).

Lingua principale
Rust
Stelle
3.7k
Fork
349
Merge medio
2g 21h
PR unite (30g)
100

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 Open-Less/openless

Tutte le issue di Open-Less/openless

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.