[Backend] Replace getDashboardStats with MongoDB aggregation to prevent OOM#438
Merged
Merged
Conversation
…t OOM getDashboardStats() used Batch.find() with no filter, loading the entire collection into memory. For large datasets this causes out-of-memory crashes. Replaced with MongoDB aggregation pipeline using , , , and for efficient server-side computation. Also added guard for null quantity values.
|
@Siddh2024 is attempting to deploy a commit to the Nitya Gosain's projects Team on Vercel. A member of the Team first needs to authorize it. |
Nitya-003
approved these changes
Jun 18, 2026
Nitya-003
added
gssoc:approved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
getDashboardStats()inbatchService.jsusedBatch.find()with no filter, limit, or projection, loading the entire Batch collection into memory. On a production dataset with millions of supply chain records, this will crash the Node.js server with an out-of-memory error. This method is called by the AI service on every relevant user query.Fixes issue #434
Changes Made
Replaced the in-memory approach with MongoDB aggregation pipeline:
$group,$sum,$addToSet, and$condfor efficient server-side computation$ifNullguard for null quantity valuescalculateStatshelper that required loading all documentsTesting
totalBatches,totalFarmers,totalQuantity,recentBatches)