[DOCS-6837] Improve troubleshooting tips related to updating large documents under WiredTiger Created: 17/Dec/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

Diagnosing performance problems due to (possibly unintentional) updates to large records could be made easier if our documentation emphasized the following points:

  • WiredTiger does no in-place updates, so large record sizes can cause much slower processing;
  • Updates to large records can delay processing for that node as the update occurs (as it has to copy the memory from one place to another and write large records to the journal)
  • This can result in high values of qr / qw / ar / aw, so if you see large values of qr / qw / ar / aw while issuing lots of updates, check that your documents are not growing to unbounded sizes.


 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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