fix: count events instead of loading them in memory #3382
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
|
After enabling |
| }), | ||
| ); | ||
| await Promise.all( | ||
| statusUpdates.map((statusUpdate) => { |
There was a problem hiding this comment.
How many queries can we potentially generate here?
| } | ||
| schedulerService.schedule( | ||
| projectService.statusJob.bind(projectService), | ||
| hoursToMilliseconds(24), |
There was a problem hiding this comment.
Doing this every 24th hour can be a scary thing, depending on the cost of this query. What happens when a customer have hundreds of projects and a lot of events?
Would love to see some data on the query cost for different setups.
There was a problem hiding this comment.
Yep, we'll provide a breakdown of the different test cases including the memory footprint in a follow up PR.
Refactor project events to use count instead of loading the events in memory