Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in
C
coderai
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • nexlab
  • coderai
  • Repository

Switch branch/tag
  • coderai
  • codai
  • api
  • pod_http.py
Find file
BlameHistoryPermalink
  • Stefy Lanza (nextime / spora )'s avatar
    raise every connection ceiling past a 128-pod fleet (v0.4.45) · 86e7f7c5
    Stefy Lanza (nextime / spora ) authored Oct 19, 2026
    A 128-pod fleet at 64 pages per pod is 8192 pages on the cards, and
    keeping the queue full behind them doubles that. Three constants each
    capped the chain below it, and the lowest one decides the fleet's
    speed whatever the others say:
    
      front -> engine forwarding pool   _FWD_MAX         8192  -> 32768
      engine -> pods async client       _MAX_FLEET_POOL  16384 -> 32768
      pod thread pool (sync transport)  _MAX_POD         8192  -> 16384
    
    All three are still sized from ocr.max_concurrency rather than set to
    their ceiling, and the pod pool is still clamped to the process's task
    budget, so this only stops a constant from being the binding limit.
    Co-Authored-By: 's avatarClaude Opus 5.5 <noreply@anthropic.com>
    Claude-Session: https://claude.ai/code/session_01KnfkxBpcZ1v6ypRFFyhrVM
    86e7f7c5
pod_http.py 11.2 KB
EditWeb IDE

Replace pod_http.py

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.