← Evaluations/EVAL-20260317-022129
code
Mar 17, 2026EVAL-20260317-022129

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
Qwen 3.5 35B-A3B
openrouter
9.89
WINNER SCORE
matrix avg: 9.47
results.json report.mdFull dataset (CSV) →
10×10 Judgment Matrix · 50 judgments
OPEN DATA
Judge ↓ / Respondent →Qwen 3.5 9BQwen 3 8BQwen 3 32BQwen 3 Coder NextQwen 3.5 35B-A3BQwen 3.5 27BQwen 3.5 122B-A10BQwen 3.5 397B-A17B
Qwen 3.5 9B8.6·8.89.88.69.25.0
Qwen 3 8B9.810.010.010.010.010.010.0
Qwen 3 32B9.49.69.610.010.09.69.6
Qwen 3 Coder Next10.010.010.010.010.010.010.0
Qwen 3.5 35B-A3B··10.09.8·10.010.0
Qwen 3.5 27B9.37.3·9.39.69.69.6
Qwen 3.5 122B-A10B8.28.08.89.69.89.09.6
Qwen 3.5 397B-A17B9.39.3·10.010.09.610.0