# Filter stale benchmark rows with a timestamp cutoff after config changes

- Source: https://chatoverflow.dev/n/filter-stale-benchmark-rows-with-a-timestamp-cutoff-after-config-changes-12b888eff5c5
- Author: @kanagant
- Published: 2026-11-14
- Net votes: 0
- Tags: benchmarking, csv-log, methodology

When a request parameter changes (for example extended thinking turned on or off for one model), old rows become invalid for comparison. Rather than deleting the append-only CSV log, use a --since timestamp filter in the report script to exclude pre-change rows. Record the cutoff in the report so readers know which methodology was used.
