Skip to content

⚡ Bolt: Optimize OllamaClient with persistent session reuse - #24

Open
Rohith-Shimori wants to merge 1 commit into
mainfrom
bolt-ollama-session-reuse-1749510183679477248
Open

⚡ Bolt: Optimize OllamaClient with persistent session reuse#24
Rohith-Shimori wants to merge 1 commit into
mainfrom
bolt-ollama-session-reuse-1749510183679477248

Conversation

@Rohith-Shimori

Copy link
Copy Markdown
Owner

⚡ Bolt: Optimize OllamaClient with persistent session reuse

💡 What:
Refactored OllamaClient to use a persistent requests.Session instead of creating new connections for every request.
Updated all methods (generate, chat, stream, etc.) to use this shared session.
Implemented proper resource cleanup for streaming responses using context managers.

🎯 Why:
Creating a new TCP connection (and SSL handshake if applicable, though usually HTTP for Ollama) for every request adds unnecessary overhead, especially for local inference where latency should be minimal.
requests.Session automatically handles connection pooling and keep-alive, significantly reducing the time-to-first-token for subsequent requests.

📊 Impact:

  • Reduces network overhead for every LLM call.
  • Improves responsiveness for chat interfaces and multi-step reasoning chains.
  • More efficient resource usage (fewer socket open/close operations).

🔬 Measurement:

  • Verified with unit tests ensuring session.post is called.
  • Verified streaming works correctly without closing the shared session prematurely.
  • Full test suite passed (with expected environment-related skips).

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

- Initialize `requests.Session` in `OllamaClient.__init__` with keep-alive
- Reuse session for `generate`, `generate_with_system`, `chat`, and streaming methods
- Update streaming methods to use `with` context manager for robust resource cleanup
- Removes connection overhead for consecutive LLM calls
- Reduces latency for high-frequency interactions

Co-authored-by: Rohith-Shimori <228351330+Rohith-Shimori@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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.

1 participant