[SERVER-34506] Add a test to verify that the isJustForContinuation future optimization kicks in with batons Created: 16/Apr/18  Updated: 29/Oct/23  Resolved: 04/May/18

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

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

Backwards Compatibility: Fully Compatible
Sprint: Platforms 2018-05-07
Participants:

 Description   

The turn your own crank continuation logic in the transport layer baton shouldn't blow the stack on many small reads.

Write a test to verify that it does not (perhaps a 16mb message streamed one byte at a time?)



 Comments   
Comment by Githook User [ 04/May/18 ]

Author:

{'email': 'jcarey@argv.me', 'name': 'Jason Carey', 'username': 'hanumantmk'}

Message: SERVER-34506 TLASIO test for isJustForContinuation

Adding an integration test for transport layer asio which uses a fail
point to induce single byte at a time reads and writes. We use this,
along with a debug block in the future header, to ensure that the
continuation folding in futures is working properly with
opportunisticRead/Write chaining.

To test the other side of this, adding a new test command called "echo"
which returns the command object passed to it (to allow for a large
message body on the read and write path more easily).
Branch: master
https://github.com/mongodb/mongo/commit/236bf5f077eb16f7bf8f0f7c5f103240bd061f12

Generated at Thu Feb 08 04:36:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.