Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.1.1
Affects Version/s: None
Component/s: Index Maintenance, Write Ops
Labels:
- graphquery

Backwards Compatibility:
Fully Compatible
Sprint:
Quint 3.1.0, Quint Iteration 3.1.1
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

IndexSpec::getKeys() finds the set of index keys for a given document and index key spec. It's used when inserting / updating / deleting a document to update the index entries, and also for performing in memory sorts, deduping $or clauses and for other purposes.

Right now extracting 10k elements from a nested object field within an array takes on the order of seconds on a decently fast machine. We could see how much we can optimize the implementation.

is duplicated by

SERVER-6904 Inner Collection (w/ > 10000 entries) with Indexed Fields Dramatically hurt performance when adding new fields on the outer document or entries in the inner collection

Closed

SERVER-9128 In place updates on documents containing indexed arrays slowing down exponentially with array size

Closed

SERVER-8954 Index Key Extraction Much Slower for Some Data Schemas Than Others

Closed

SERVER-11699 Update command: unexpected performance

Closed

related to

SERVER-14037 Parallel arrays in distinct sub-documents no longer cause an indexing error

Closed

SERVER-8193 Optimize in place updates that modify an index (not to deteriorate based on size of a different indexed field)

Closed

(1 related to)

Assignee:: David Storch

Reporter:: Aaron Staple (Inactive)

Participants:: A. Jesse Jiryu Davis, Aaron Staple, Asya Kamsky, David Storch, Githook User

Votes:: 32 Vote for this issue

Watchers:: 45 Start watching this issue

Created:: Jan 16 2013 06:42:18 PM UTC

Updated:: Dec 08 2015 11:01:45 PM UTC

Resolved:: Mar 31 2015 10:35:01 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates