Skip to content

⚡ Bolt: Optimize OllamaClient connection reuse - #19

Draft
google-labs-jules[bot] wants to merge 1 commit into
mainfrom
bolt/ollama-connection-reuse-3176438193679347593
Draft

⚡ Bolt: Optimize OllamaClient connection reuse#19
google-labs-jules[bot] wants to merge 1 commit into
mainfrom
bolt/ollama-connection-reuse-3176438193679347593

Conversation

@google-labs-jules

Copy link
Copy Markdown
Contributor

💡 What:

  • Implemented persistent requests.Session in OllamaClient (core/ollama_client.py).
  • Replaced individual requests.post calls with self.session.post in generate, chat, and stream methods.
  • Refactored stream method to use the shared session while preserving specific headers for event streaming.

🎯 Why:

  • Previously, every API call to Ollama established a new TCP connection (handshake overhead).
  • For a local LLM client making frequent requests (chat, generation, streaming), this adds unnecessary latency.

📊 Impact:

  • Eliminates TCP handshake latency for subsequent requests (measurable in milliseconds per request, significant for high-frequency interaction).
  • Reduces system resource usage (socket creation/teardown).

🔬 Measurement:

  • Verified using a reproduction script that mocks requests and confirms session.post is used instead of requests.post.
  • Confirmed proper header handling in streaming requests.

PR created automatically by Jules for task 3176438193679347593 started by @Rohith-Shimori

- Initialize `requests.Session` in `OllamaClient.__init__`
- Use `self.session.post` for `generate`, `chat`, and `stream` methods
- Prevent new TCP connection establishment for every API call
- Reuse connection for streaming with correct headers
@google-labs-jules

Copy link
Copy Markdown
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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.

0 participants