Menu

1 / 5

Why a 0.86 ms Qdrant Query Timed Out at 60 Seconds in Our Script

DEV Community: typescript·Utkarsh Gupta·6 days ago
#Ny1koXne
#devtotypescript#devto#dev#index#branch
Reading 0:00
15s threshold

TL;DR

A slow request doesn't always mean a busy server. Time one request on its own before you blame load.

An index only helps when your question matches what the index stores. Ask a text index for a number and the database can't use it.

In an "either this or that" search, one half that can't use the index can make the whole search read everything.

Check how a field is really indexed by asking the database, not by trusting memory or a guess.

A script that prints "updated" for every document tells you nothing. Log what actually changed.

A one-off script kept timing out. Every lookup waited the full 60 seconds and gave up. Yet when I timed one lookup on the same field by hand, the server answered in 0.86 ms.

You've probably met this at a library desk. Ask for a book by its title and the answer comes back in seconds, because the catalogue is sorted by title.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.