8000
  • feat: skip redundant openai request serialization by SasSwart · Pull Request #160 · coder/aibridge · GitHub
    [go: up one dir, main page]

    Skip to content

    feat: skip redundant openai request serialization#160

    Merged
    SasSwart merged 9 commits intomainfrom
    jjs/appendCompact
    Feb 2, 2026
    Merged

    feat: skip redundant openai request serialization#160
    SasSwart merged 9 commits intomainfrom
    jjs/appendCompact

    Conversation

    @SasSwart
    Copy link
    Contributor
    @SasSwart SasSwart commented Feb 2, 2026

    Apply openai/openai-go#602 to reduce allocations and allocated bytes for all openAI interceptions.

    Also use gjson instead of a full unmarshal to determine whether or not to use the streaming API.

    Copy link
    Collaborator
    @dannykopping dannykopping left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    LGTM

    @SasSwart SasSwart merged commit 9e2857a into main Feb 2, 2026
    4 checks passed
    SasSwart added a commit to coder/coder that referenced this pull request Feb 2, 2026
    … bridge (#21838)
    
    Apply optimizations:
    * openai/openai-go#602
    * coder/aibridge#160
    
    These reduce CPU time and allocation count for OpenAI `chat/completions`
    and `responses` APIs, making the use of OpenAI chat models through AI
    Bridge more performant.
    
    In order to test these changes, we add scaletesting support for the
    responses API.
    SasSwart added a commit to coder/coder that referenced this pull request Feb 3, 2026
    … bridge (#21838)
    
    Apply optimizations:
    * openai/openai-go#602
    * coder/aibridge#160
    
    These reduce CPU time and allocation count for OpenAI `chat/completions`
    and `responses` APIs, making the use of OpenAI chat models through AI
    Bridge more performant.
    
    In order to test these changes, we add scaletesting support for the
    responses API.
    Sign up for free to join this conversation on GitHub. Already have an account? 63C6 Sign in to comment

    Labels

    None yet

    Projects

    None yet

    Development

    Successfully merging this pull request may close these issues.

    2 participants

    0