Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

Local GPU server benchmarks 12 models from 4B to 35B parameters

AI summary

A Reddit developer says they built a Linux server with two RTX 5060 Ti cards providing 32 GB of total VRAM, running vLLM in Docker. The developer reports testing 12 models from 4B to 35B parameters on complete datasets including IFEval, IFBench, ARC AGI 1, SimpleQA, SimpleQA Verified and SciCode, both with thinking enabled and disabled. The system also records wall-clock duration and token throughput to produce a time-efficiency score, although the methodology and results are self-reported.

In-depth insight

The project provides a local-hardware benchmark that combines full-dataset results with runtime and throughput measurements for models between 4B and 35B parameters.

Hi everyone, whenever I looked at existing LLM leaderboards I was missing practical numbers for running quantized open weight models on affordable local hardware. Most tables only copy vendor cloud scores or run tiny subsets of a benchmark, and none of them tell you how long a model actually sits there calculating before it finishes. Because nothing like that existed, I set up a dedicated Linux test server with two RTX 5060 Ti cards giving 32 GB of VRAM in total, running vLLM in Docker. Over the past weeks I ran 12 current local models from 4B up to 35B through complete benchmark datasets without any subsampling, including IFEval, IFBench, ARC AGI 1, SimpleQA, SimpleQA Verified, SciCode and vLLM bench serve. The lineup includes Qwen 3.5, Qwen 3.6 and Qwen 3.8 in 4B, 9B, 27B and 35B A3B, Google Gemma 4 in E4B, 26B A4B and 31B, plus GLM 4.7 Flash in 4 bit quantizations like NVFP4 and AWQ.

Every single model is tested twice across all benchmarks, once with thinking turned off and once with thinking turned on, using the official sampling parameters. While the tests run, my system tracks the exact wall clock duration and throughput in tokens per second to calculate a time efficiency score from 0 to 100 for every single cell. That turned out to be the most interesting part of the whole project. You can immediately see which models deliver strong scores in 20 or 30 minutes and which ones burn GPU power for 10 hours straight because they get stuck reasoning in circles on simple questions. Especially the MoE models like Qwen 3.6 35B A3B and Gemma 4 26B A4B surprised me by finishing in a fraction of the time while beating or matching the dense 27B and 31B models.

#Local GPU Benchmark Server#vLLM#NVIDIA RTX 5060 Ti#Qwen 3.5#Qwen 3.6#Qwen 3.8#Google Gemma 4#GLM 4.7 Flash

Original · 2 min readRead the original
Group chat

No comments yet. Start the conversation.