Held-history compatibility replay · cold and warm requests
DeepSeek V4.1 Flash 1017 · EXL3 · normal
NVIDIA DGX Spark
- prompt tokens
- 63,164
- history messages
- 220
- complete tool pairs
- 110
All measurements & context
- prompt tokens
- 63,164
- history messages
- 220
- complete tool pairs
- 110
- cold wall
- 43.9 s
- warm wall
- 8.8 s
- warm cached tokens
- 61,440
- structured responses passed
- 2
- requests attempted
- 2
Measured compatibility/cache observation. Two high-reasoning requests used a copy of an existing 220-message history with 110 complete tool-call/result pairs. Both returned valid structured responses; tools were not executed.
Protocol: Replay the same copied history twice against the new native model without changing the original held session or executing proposed tools. Record total prompt length, response structure, request wall time and second-request cache usage. The warm request reported 61,440 cached positions out of 63,164 input positions.
Limits: One copied conversation and two requests, with no repeat spread, task-success grading or retrieval test. These wall times are not TTFT measurements. Cache reuse does not qualify the configured 524,288-position window, other conversations, or simultaneous full-context requests. Private history text is not published.
Source: Dated copied-history compatibility receipts · October 23, before the 03:57 CDT loop resume
Runtime: TensorFold native · TP2 · high reasoning
Source record updated 2026-10-23