Skip to content

⚡ Bolt: Implement gRPC client caching for Cloud Run APIs#18

Open
JulienBreux wants to merge 2 commits into
mainfrom
bolt-grpc-client-caching-6540545671437153499
Open

⚡ Bolt: Implement gRPC client caching for Cloud Run APIs#18
JulienBreux wants to merge 2 commits into
mainfrom
bolt-grpc-client-caching-6540545671437153499

Conversation

@JulienBreux

Copy link
Copy Markdown
Owner

Implemented thread-safe lazy-initialization and caching for GCP clients in all internal/run/api packages to reduce latency and redundant authentication overhead. Verified with full test suite.


PR created automatically by Jules for task 6540545671437153499 started by @JulienBreux

This optimization implements a thread-safe lazy-initialization and caching
pattern for GCP clients across all resource types (services, jobs, worker
pools, domain mappings, and executions).

Previously, a new GCP client was created and closed for every single API call.
By caching these clients, we reuse the underlying gRPC/REST connections and
avoid redundant credential discovery and authentication overhead.

Measurable impact:
- Significant latency reduction for multi-region operations (e.g., listing
  services across all 24+ regions).
- Reduced load on the Google Cloud Authentication service.
- Smoother TUI experience during rapid navigation.

Tests:
- Package-specific tests for each client.
- Full project test suite (make test).
- Manual verification of TUI responsiveness.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

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

This commit introduces two main changes:
1. Performance Optimization: Implemented a thread-safe lazy-initialization
   and caching pattern for GCP clients across all resource types. This
   significantly reduces latency by reusing gRPC connections and avoiding
   repeated authentication overhead.
2. CI Fix: Updated the goreleaser workflow to use the --snapshot flag
   when running on pull requests, preventing failures due to missing git
   tags or mismatched commits.

All changes have been verified with the full test suite and code review.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
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