[CDRIVER-2343] /BulkOperation/numerous tests are time-consuming Created: 06/Nov/17  Updated: 28/Oct/23  Resolved: 26/Apr/18

Status: Closed
Project: C Driver
Component/s: libmongoc, tests
Affects Version/s: 1.9.0
Fix Version/s: 1.10.0

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to CDRIVER-2376 Performance loss with small reads and... Closed
Epic Link: Post-3.6 Optimization

 Description   

The tests /BulkOperation/numerous_ordered and /BulkOperation/numerous_unordered each execute 3 bulk operations that are over 4 times the max batch size. That was a bit time-consuming when the max batch size was 1000, but with 3.6's batch size of 100k, the two tests take almost a minute each to do 100k * 4 * 3 = 1.2 M operations.

Is it expected that each test takes almost a minute to do 1.2 M operations? Seems slow compared to my rule of thumb that a driver can do 50k simple operations per second on localhost, that should take less than 30 seconds.



 Comments   
Comment by Githook User [ 26/Apr/18 ]

Author:

{'email': 'jesse@mongodb.com', 'username': 'ajdavis', 'name': 'A. Jesse Jiryu Davis'}

Message: CDRIVER-2343 faster maxWriteBatchSize tests
Branch: master
https://github.com/mongodb/mongo-c-driver/commit/671cb902a47cf01bfb7a549ea3030c01b56026f7

Comment by A. Jesse Jiryu Davis [ 07/Nov/17 ]

Could also delete the test in favor of a mock test that pretends the max batch size is tiny.

Comment by A. Jesse Jiryu Davis [ 07/Nov/17 ]

Possible approach: make a slow nightly test for the C Driver.

Comment by Githook User [ 07/Nov/17 ]

Author:

{'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}

Message: CDRIVER-2343 optionally skip lengthy bulk tests
Branch: master
https://github.com/mongodb/mongo-c-driver/commit/8c9bd140f7a9da27e34fcf8fabfccd9a7491d0ad

Generated at Wed Feb 07 21:14:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.