perf: Refactor bookings queries for API
What does this PR do?
Seeing that pulling bookings takes around 600ms on our prod db and it's because we use an 'OR' when looking for attendees. Splitting it out is much faster.
Mandatory Tasks (DO NOT REMOVE)
- [x] I have self-reviewed the code (A decent size PR without self-review might be rejected).
- [x] N/A I have added a Docs issue here if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
- [x] I confirm automated tests are in place that prove my fix is effective or that my feature works.
How should this be tested?
- Ensure all API automated tests pass and ensure that pulling data for bookings is not impacted
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| cal-com-ui-playground | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | May 7, 2025 6:22pm |
2 Skipped Deployments
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| calcom-web-canary | ⬜️ Ignored (Inspect) | Visit Preview | May 7, 2025 6:22pm | |
| cal | ⬜️ Skipped (Inspect) | May 7, 2025 6:22pm |
LGTM. Waiting on checks.
Closing and reopening because the checks just stopped working for some reason
This PR is being marked as stale due to inactivity.
This PR is being marked as stale due to inactivity.
Closing since this is stale, v1 is deprecated and Fluid Compute has made usage going way down. No need to introduce the risk here.
The failing dev build was due to OOM issue on Vercel. Redeploying.