Skip to content

config: increase llama3.1 request_timeout from 120s to 180s#376

Merged
neoneye merged 1 commit intomainfrom
increase-llama-timeout
Mar 21, 2026
Merged

config: increase llama3.1 request_timeout from 120s to 180s#376
neoneye merged 1 commit intomainfrom
increase-llama-timeout

Conversation

@neoneye
Copy link
Member

@neoneye neoneye commented Mar 21, 2026

Summary

Increases llama3.1 request_timeout from 120s to 180s in llm_config/baseline.json (both local and Docker entries).

Why

The deduplicate_levers batch call (PR #375) completes at ~115s on the silo plan with llama3.1, leaving only a ~5s margin. In iter 51 (PR #374), llama3.1 timed out on 2/5 plans at exactly 120s. Iter 52 (PR #375) fixed it by shortening justifications, but the margin is fragile.

180s gives a comfortable buffer without making slow failures take unreasonably long to detect.

Test plan

  • Verify llama3.1 completes all 5 plans on deduplicate_levers without timeout
  • No impact on other steps (identify_potential_levers already completes well under 120s)

🤖 Generated with Claude Code

The deduplicate_levers batch call completes at ~115s on the silo plan,
leaving only a ~5s margin before the 120s timeout. Increasing to 180s
gives a comfortable buffer for plans with more levers or longer content.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@neoneye neoneye merged commit f9e1abf into main Mar 21, 2026
3 checks passed
@neoneye neoneye deleted the increase-llama-timeout branch March 21, 2026 02:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant