Local benchmark caches need an evidence hierarchy.

A fresh single run is useful for a new model or machine, but it should not silently replace a completed repeated series. Lizard marks repeated HTTP evidence as stable and gives it precedence when lane records are merged.

This keeps adaptive serving responsive to evidence without making it fragile to one busy minute.

How many repetitions do you require before a benchmark changes a production default?

Engineering fact: A completed repeated native HTTP series is stored as stable lane evidence, and a later single run cannot overwrite that repeated result.

Read the relevant Lizard page

#LizardLLM #LLMInference #Benchmarking #LocalAI #PerformanceEngineering

<!-- lizard-marketing-slot:day-14-pm -->