benchmarking

ChromaDB OOM error during high-throughput vector insertion benchmarking

by
a rack of servers in a server room

Problem: OOM Errors During High‑Throughput Vector Insertion Benchmarking When benchmarking ChromaDB on a single‑node VM (16 GB RAM, 8 vCPU) with 10 M+ 768‑dimensional embeddings, the Python process is terminated by the kernel after a few gigabytes of RSS growth. Typical failure messages observed include: MemoryError: Unable to allocate 1.2 GiB sqlite3.OperationalError: database or disk is full OSError: … Read more

OpenAI GPT-4 OAuth2 flow interrupted during high volume API benchmarking

by
a computer screen with a web page on it

Problem Description During an automated performance benchmark of the OpenAI GPT‑4 endpoint, a custom Python script launches hundreds of concurrent requests to measure throughput and latency. After a short ramp‑up period (≈30 seconds) the benchmark is interrupted by a surge of HTTP 401 Unauthorized responses. The script retries the failed calls, but each retry also receives 401, … Read more

Elasticsearch ReplicaSet scaling failure during benchmarking

by
a close-up of a server room

Problem: Replica Set Scaling Failure During Elasticsearch Benchmarking During a performance benchmark on a multi‑node Elasticsearch cluster, replica shards do not scale up or down in response to the predefined desired replica count metrics. The symptoms observed include: After adding two new data nodes, replica shards remain on a single node, causing CPU saturation on … Read more

Milvus ReplicaSet scaling failure during high concurrency benchmarking

by
A red kite soars against a green forest.

Problem – Milvus ReplicaSet Scaling Failure Under High‑Concurrency Benchmark During a distributed performance benchmark of Milvus 2.x, the team attempted to increase the replicaCount of the QueryNode (and optionally the Proxy) to meet a target query throughput of ~10 k QPS. The scaling operation consistently failed: New QueryNode pods remained in Pending or entered CrashLoopBackOff. Existing … Read more