A workstation can run one model comfortably and still fall short in the workflow you plan to ship. A useful evaluation starts with the work your application will request. Write down the model, quantization, context size, number of simultaneous requests and the maximum wait a user should tolerate before seeing the first token. Save those settings beside the test results so that someone else can repeat the run.
Start with a single prompt and then run the same request after the model has loaded. Track time to first token separately from tokens per second during decoding. For a chat interface, the first number helps explain how responsive the app feels. For a report generator, the total completion time may matter more. If your app sends a long document, add a second test close to the largest input you expect. Use the same model and input across the machines you compare.
Use the benchmark only to compare the same workload. The llama-bench documentation explains how to report prompt processing and text generation separately. Keep a second test that measures the latency your application actually exposes to a user. Next, watch the machine under the workload it will actually share. Keep your editor, browser and the expected background services open. Run repeated requests for a set period and track latency alongside memory use. Record whether the model spills into a slower memory tier or the system begins swapping. If your workflow uses a second model for embeddings, leave that model resident during the test. A small single-model benchmark will miss that contention.
Before buying or provisioning anything, map those measurements to the specification sheet. Use a compact desktop specification example to identify the fields to compare across small systems. Confirm the exact configuration with its vendor and check software support for your own runtime. Treat vendor capacity figures and your measured headroom as separate entries in the worksheet.
Finish with a one-page decision record. Include the test date, runtime version, input size, cold and warm measurements, and one reason a configuration fails. Save the prompt and settings so the same harness can guide a later upgrade or catch a regression after a runtime change.