[SERVER-53527] libdeps visualizer: backend should have a memory limit option Created: 28/Dec/20  Updated: 29/Oct/23  Resolved: 25/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Daniel Moody Assignee: Daniel Moody
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Dev Platform 2022-07-25
Participants:

 Description   

Currently the backend will load graphs into memory unlimited, until out of memory occurs and the backend crashes.

 

The backend should have an option to set the max memory it is allowed to use for graph allocation. Currently each graph is cached as it stored, so that it doesn't need to reload a given graph if the frontend requests analysis for that graph. The load time for a graph is several seconds so its not desirable to always reload them.

 

The storage of the graphs into the backends application memory should use a least recently used algorithm for removing graph data to make room for new graph data in order to stay under the memory limit. However the algorithm to use is up for debate if any one has better ideas.



 Comments   
Comment by Githook User [ 25/Aug/22 ]

Author:

{'name': 'Daniel Moody', 'email': 'daniel.moody@mongodb.com', 'username': 'dmoody256'}

Message: SERVER-53527 Memory limit for libdeps visualizer backend
Branch: master
https://github.com/mongodb/mongo/commit/6bb42b80d6846b25376c1415438b756a0ce6418b

Comment by Alex Neben [ 16/Aug/22 ]

going to try and get this in by tomorrow

Generated at Thu Feb 08 05:31:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.