Set reasoning-budget 16384; measurement shows it buys nothing here
Deployed as requested, then verified. On the same problem 4096 and 16384
give the same correct answer, but 16384 uses 17417 tokens instead of 5325
(~6 min vs ~2 min) and spends the extra budget in a repetition loop
("Maybe it's a^2+b^2=c^2+7?" repeated) rather than converging.
The premise for raising it -- thinking was truncated, so it needs room --
did not survive measurement. Documented; the value is left at 16384 as
requested rather than reverted unilaterally.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
+5
-1
@@ -57,8 +57,12 @@ services:
|
||||
# generate until the 128k window is full: ~50 min blocking the single slot.
|
||||
- --predict
|
||||
- "32768"
|
||||
# Hard server-side ceiling on the thinking block — a client CANNOT raise it
|
||||
# per request (verified). Note the README measurement: on the test problem
|
||||
# 4096 and 16384 produced the SAME correct answer, but 16384 burned 3.3x the
|
||||
# tokens looping. 4096 is defensible; revisit if real workloads disagree.
|
||||
- --reasoning-budget
|
||||
- "4096"
|
||||
- "16384"
|
||||
- --slot-save-path
|
||||
- /slots
|
||||
- --jinja
|
||||
|
||||
Reference in New Issue
Block a user