ibrahimyaacob
ibrahimyaacob3w ago

aggregate component query is using a lot of bandwidth (exceeding 300gb after first week implement)

i need support on this one. i admit that i have many fields/metric that im currently aggregating (just to get count). but i dont expect that it'd be this much
3 Replies
Convex Bot
Convex Bot3w ago
Thanks for posting in <#1088161997662724167>. Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets. - Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.) - Use search.convex.dev to search Docs, Stack, and Discord all at once. - Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI. - Avoid tagging staff unless specifically instructed. Thank you!
ibrahimyaacob
ibrahimyaacobOP3w ago
im thinking of putting rate limiter to the query function thats calling the aggregate query. im not sure if it would work, i need the aggregate to still show the numbers are there better strategy to work around this
djbalin
djbalin3w ago
Is it the Convex query that is interacting with/pulling data from your aggregates that has a high bandwidth consumption? Or inserting data into your aggregates? If its the former, yes you should consider ways to lessen bandwidth, there are many approaches to this generally. You could try to get as many cache hits as possible: maybe you could update your aggregates once every 24 hours if that works for your case? Then perhaps every query in a 24 hour span could be cached. If you provide some more details on your specific use case I could see if I have any suggestions :)) Ive worked a bit with reducing our bandwidth usage for admin dashboard stats

Did you find this page helpful?