⚡ Bolt: Optimize Traffic Dashboard caching#54
Conversation
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
💡 What: Replaced direct database query
prisma.cachedModel.findManywith the existing cached methodmodelCatalog.getCachedPoolModels()inPoolController.getTraffic().🎯 Why: The traffic dashboard frequently polls this endpoint, resulting in unnecessary database reads for static or slow-changing model metadata (like prices).
📊 Impact: Reduces database load by eliminating one query per poll interval for the
/api/pool/trafficendpoint. The in-memory cache automatically refreshes asynchronously when needed.🔬 Measurement: Verify by watching DB queries. The
/api/pool/trafficrequest should no longer trigger afindManyquery against theCachedModeltable.PR created automatically by Jules for task 15249728262395817595 started by @zaydiscold