[COMPASS-1764] Compass handles the crazy keys document series Created: 18/Aug/17 Updated: 27/Oct/23 Resolved: 01/Oct/18 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | CRUD, Performance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Peter Schmidt | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Epic Link: | COMPASS-1739 |
| Story Points: | 5 |
| Description |
Usage/steps to reproduce
Then navigate to the perf.crazy_keys collection in Compass. An extended set of documents can be created and imported into MongoDB with this script relatively easily, on my local machine I already have the following numbers of keys and preliminary results: Proposed solution - cap at 100k fields#intellectualhonesty - let the data drive your decision. Thus Compass, most likely in mongodb-schema, should stop scanning at about 100k fields (configurable as other optimizations are found) in a document and report this Easter egg in the GUI (originally this was Issue 2 in Acceptance criteria
Out of scope
BackgroundSo I let Friday afternoon get to me and challenged myself to create a document with ~2.7 million keys. After about 3 minutes, Compass crashes. The mongo shell is still doing something in CPU-land after 8 minutes so far. On different data sets, such as documents with ~500,000 fields (i.e. Would explicitly limiting Compass to say 100,000 fields with a message like "Compass cannot render documents with more than 100,000 fields" seem reasonable? Yes but only when the user gets down to the 100,001st field. For documents under 100k fields, is a loading spinner enough? (i.e. ~6 seconds, so should not need a progress bar?). Proposed Solutions: Potentially push to the GPU? Otherwise just drop to Loading... text. |
| Comments |
| Comment by Durran Jordan [ 01/Oct/18 ] |
|
Rewriting stories to remove hadron-document |
| Comment by Peter Schmidt [ 18/Aug/17 ] |
|
I think it's safe to say for this synthetic example, wont fix (at least for now, and especially as the Mongo shell doesn't work either). EDIT: Compass should never crash (that would be a bug if reported by a user), so this issue does need to be handled explicitly. Ticket has accordingly been repurposed into a task broken out of discussion which started on |