Generate a 2,000 token report.
Many engineers place NGINX or Cloudflare Tunnel in front of their LLM. Run LANBench directly to the LLM server, then run it again via the proxy. If token speed drops by 30%, you know your proxy configuration is the bottleneck.
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.
Assuming a compiled version of LANBench (syntax varies by fork, but typical):
Start server (on 192.168.1.100):
lanbench -s -p 5001
Run client for 30 seconds, bidirectional test, 1500-byte MTU:
lanbench -c 192.168.1.100 -p 5001 -t 30 -b 1500 -d both
Sample output (client side):
Connecting to server 192.168.1.100:5001
Test duration: 30 sec, Buffer: 65536 bytes, Direction: both
[ ID] Interval Transfer Bandwidth
[ 1] 0.00-30.00 sec 37.2 GBytes 10.65 Gbits/sec (send)
[ 1] 0.00-30.00 sec 37.0 GBytes 10.59 Gbits/sec (recv)
Tagline: "The Ultimate Local Area Network Stress Test."
LANBench operates using a Client-Server model.
You have a 70B parameter model. You can run it quantized to 4-bit (faster, less accurate) or 8-bit (slower, more accurate). Run LANBench with both configurations:
LANBench is a lightweight, cross-platform utility designed to measure throughput and latency between two nodes on a Local Area Network (LAN). It functions on a client-server model, allowing IT administrators and network engineers to validate link speeds, test cable quality, and diagnose bottlenecks without the need for complex hardware analyzers.
