[COMPASS-422] mongodb-schema: provide a memory limit parameter Created: 22/Nov/16 Updated: 10/Jan/24 Resolved: 27/Sep/19 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Epic Link: | COMPASS-2234 | ||||||||||||
| Description |
|
mongodb-schema should take a memory limit parameter and stop analysing the schema when that limit is reached. It could either (a) stop adding values and simply update counts/probabilities, or (b) stop sampling documents alltogether. It should probably also contain a top-level field "memoryLimitReached: true", so that Compass can give the user some feedback. This work has already been started as part of COMPASS-218 but is too risky to merge for 1.5 stable. Re-visit after 1.5 was released. |
| Comments |
| Comment by Massimiliano Marcon [ 27/Sep/19 ] |
|
Closing this issue in JIRA. It's been moved to the new, unified feedback engine at https://feedback.mongodb.com/forums/924283-compass. We are looking for input to decide how to prioritize it, so go there, look for the suggestion, vote and leave comments. If you don't find it, feel free to create a new one. |
| Comment by Brian Blevins [ 29/Mar/17 ] |
|
Customer feedback on Compass memory utilization. 00432392: Using too much memory for large collection 2017-July-17:
|
| Comment by Thomas Rueckstiess [ 22/Nov/16 ] |
|
Current (unfinished) implementation: https://github.com/mongodb-js/mongodb-schema/tree/COMPASS-422-memory-limit |
| Comment by Githook User [ 22/Nov/16 ] |
|
Author: {'name': 'Thomas Rueckstiess', 'email': 'thomas@rueckstiess.net', 'username': 'rueckstiess'}Message: |