Lanbench -

If a file transfer across the office is slow, LANBench can determine if the issue is the network or the storage medium (hard drives). If LANBench shows high throughput but file copying is slow, the bottleneck is likely disk I/O, not the network.

A lightweight orchestration script (usually Go or Rust for concurrency) that manages test cases. It loads a prompt dataset (e.g., dialogues.json or code_gen.json), defines concurrency levels, and sends requests.

When you first run LANBench, you will likely see disappointing numbers. Here is how to fix them: LANBench

Pitfall 1: High TTFT (Over 2 seconds)

Pitfall 2: Intermittent Timeouts

Pitfall 3: Low Throughput at Concurrency 1

Execute the client:

./lanbench run --config benchmark.yaml --output results.json

Before LANBench gained traction, engineers relied on tools like text-generation-webui’s built-in stats or llama.cpp’s --benchmark flag. These tools have a fatal flaw: they measure internal compute speed.

Consider this scenario:

Standard benchmarks would report "100 t/s." LANBench would report the truth: "65 t/s due to network jitter and JSON parsing."

LANBench is a benchmarking tool designed to measure and analyze the performance of Local Area Networks (LANs). It evaluates throughput, latency, packet loss, jitter, and protocol behavior under varying traffic patterns to help network engineers quantify performance, identify bottlenecks, and validate configuration or hardware changes. If a file transfer across the office is