← Evaluations/EVAL-20260315-034630
code
Mar 15, 2026EVAL-20260315-034630

Your Node.js API is responding with 502 errors under load. Here's the relevant code and infrastructure: - Express.js API behind an Nginx reverse proxy - Connection pool to PostgreSQL (max 20 connections) - Average response time: 50ms normally, 30s+ during incidents - Error logs show: "connect ETIMEDOUT" and "too many clients already" - The issue starts when traffic exceeds 200 req/s ```javascript app.get('/api/users/:id', async (req, res) => { const client = await pool.connect(); const result = await client.query('SELECT * FROM users WHERE id = $1', [req.params.id]); res.json(result.rows[0]); }); ``` What's wrong? Provide the fix and explain the connection pool exhaustion pattern.

Winner
Kimi K2.5
openrouter
9.57
WINNER SCORE
matrix avg: 8.97
results.json report.mdFull dataset (CSV) →
10×10 Judgment Matrix · 83 judgments
OPEN DATA
Judge ↓ / Respondent →Qwen 3 32BKimi K2.5Devstral SmallGemma 3 27BLlama 4 ScoutPhi-4 14BGranite 4.0 MicroQwen 3 8BMistral Nemo 12BLlama 3.1 8B
Qwen 3 32B9.68.49.69.18.88.39.68.08.4
Kimi K2.5···5.8····3.0
Devstral Small9.110.09.88.68.88.69.68.88.6
Gemma 3 27B8.79.89.49.89.89.49.89.89.2
Llama 4 Scout9.49.88.69.89.39.39.68.88.2
Phi-4 14B9.89.89.39.89.09.210.09.48.6
Granite 4.0 Micro8.48.88.88.88.88.88.88.88.4
Qwen 3 8B7.810.08.89.69.410.010.09.49.0
Mistral Nemo 12B8.38.88.28.88.18.28.19.48.1
Llama 3.1 8B8.89.69.19.69.49.18.68.89.1