Skip to content

Performance: Batch Google Calendar Fetching#5

Draft
google-labs-jules[bot] wants to merge 1 commit intomasterfrom
perf/optimize-calendar-fetching-6894858907708110257
Draft

Performance: Batch Google Calendar Fetching#5
google-labs-jules[bot] wants to merge 1 commit intomasterfrom
perf/optimize-calendar-fetching-6894858907708110257

Conversation

@google-labs-jules
Copy link

This PR addresses the performance bottleneck in popupEvents.vue where calendar events were fetched sequentially in a loop.

Changes:

  1. Backend (electron/GoogleApi.ts): Added useGetBatchCalendarEvents which accepts an array of calendar IDs. It processes them in chunks of 5 using Promise.all to balance parallelism with rate limiting.
  2. IPC (electron/process.ts): Exposed getBatchCalendarEvents handler.
  3. Frontend (src/composables/util.ts): Added client-side wrapper useGetBatchCalendarEvents.
  4. Frontend (src/pages/main/components/popupEvents.vue): Refactored init method to aggregate checked calendar IDs and make a single batch call. Logic for accessCount was updated to handle the single callback correctly.

Performance:
A simulation showed a reduction from ~5000ms to ~1000ms for 25 calendars (assuming 200ms latency), primarily due to parallelization.

Verification:

  • Ran vue-tsc to ensure type safety.
  • Verified logic via code review and simulation.

PR created automatically by Jules for task 6894858907708110257 started by @LETS-BEE

- Implemented `useGetBatchCalendarEvents` in backend to fetch events for multiple calendars in parallel.
- Added concurrency control (chunk size 5) to respect API rate limits/costs.
- Updated `popupEvents.vue` to use the new batch API instead of looping N times.
- Significantly reduced IPC overhead and total fetch time (verified via simulation).
@google-labs-jules
Copy link
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