⚡ Bolt: Optimize sitemap generation with parallel fetching

[anyulled]

💡 What: Replaced sequential data fetching loops inside app/sitemap.ts with parallel Promise.all fetching.
🎯 Why: Generating the sitemap was slow because it sequentially fetched speakers and talks for each edition year one by one (O(N * (time_speakers + time_talks))).
📊 Impact: Accelerates sitemap generation significantly by executing API requests concurrently. Build time goes from O(N * (time_speakers + time_talks)) down to O(max(time_speakers, time_talks)).
🔬 Measurement: Measured local execution time or build times via next build to confirm improved SSG compilation time. Tests successfully ran to verify URLs output identically.

---

PR created automatically by Jules for task 6804994286810769814 started by @anyulled

Summary by CodeRabbit

• Refactor
  • Enhanced sitemap generation performance by fetching speaker and session data concurrently instead of sequentially for each year.
  • Improved error resilience with better exception handling for data retrieval failures.

[google-labs-jules]

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
devbcn	Building	Preview, Comment	Mar 2, 2026 10:25am

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request optimizes the sitemap generation process by refactoring data fetching logic. It transitions from a sequential approach, where speaker and talk data for each year were fetched one by one, to a parallel execution model using Promise.all. This change aims to drastically reduce the time required to build the sitemap by concurrently making API requests, thereby improving overall build performance.

Highlights

• Parallel Data Fetching: Replaced sequential loops for fetching speakers and talks with Promise.all to fetch data for all years concurrently, significantly speeding up sitemap generation.
• Performance Optimization: Reduced sitemap build time complexity from O(N * (time_speakers + time_talks)) to O(max(time_speakers, time_talks)) by parallelizing API requests.

Changelog

• app/sitemap.ts
  • Implemented parallel fetching for speakers and talks across all years using Promise.all.
  • Removed redundant sequential data fetching calls within the year iteration.

Activity

• PR created automatically by Jules for task 6804994286810769814, started by @anyulled.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fca6a1c and 4b5094b.

📒 Files selected for processing (1)

• app/sitemap.ts

---

📝 Walkthrough

Walkthrough

The PR optimizes sitemap data fetching by replacing sequential per-year fetches with concurrent fetches using Promise.all. Speakers and sessionGroups are now fetched in parallel for each year with .catch() error handling, and the aggregated data is preprocessed into a yearsData array before the main processing loop.

Changes

Cohort / File(s)	Summary
Concurrent Sitemap Data Fetching app/sitemap.ts	Refactored data fetching from sequential to concurrent pattern. Introduced yearsData array to precompute speakers and sessionGroups per year using Promise.all with error handling. Updated processing loop to consume precomputed data instead of inline fetches.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• ⚡ Bolt: optimize homepage speakers fetching #27: Related modification to speaker data fetching patterns, moving getSpeakers usage to server pages and hooks alongside this concurrent optimization.

Poem

🐰 Hops of joy for faster hops!
Concurrent fetches, never stops!
Promise.all speeds up the race,
Aggregated data fills the space! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: optimizing sitemap generation through parallel fetching, which directly aligns with the primary objective of replacing sequential fetches with concurrent aggregation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bolt-sitemap-parallel-fetch-6804994286810769814

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request introduces a significant performance optimization to the sitemap generation process. By replacing sequential fetching in a loop with parallel Promise.all calls, the data for all years' speakers and talks are fetched concurrently. This change will drastically reduce the time required to generate the sitemap. The implementation is robust, including error handling for individual fetches to prevent complete failure. The code is clean and effectively achieves its goal. I have no further suggestions for improvement.