[SERVER-11573] conc_update.js timing out on Windows 64-bit 2008R2+ Created: 05/Nov/13  Updated: 11/Jul/16  Resolved: 20/Dec/13

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 2.5.5

Type: Bug Priority: Major - P3
Reporter: sam.helman@10gen.com Assignee: hari.khalsa@10gen.com
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 64-bit 2008R2+


Operating System: ALL
Participants:

 Description   

This has been happening consistently.

Here is the first commit where it timed out:
https://mci.10gen.com/ui/task/mongodb_mongo_master_windows_64_2k8_beaeb05efd7f70cb7885555be36d47b8beb2d2be_13_11_03_16_50_06_slow_weekly_tests_windows_64

Here is the commit directly before the one above. It actually fails in this commit, and then times out in subsequent commits:
https://mci.10gen.com/ui/task/mongodb_mongo_master_windows_64_2k8_83e056702108e7693e58886a8364aaa036eb6edd_13_11_03_00_09_05_slow_weekly_tests_windows_64

It also failed in this commit, a few back from the one above. This creates the possibility the test could be flaky:
https://mci.10gen.com/ui/task/mongodb_mongo_master_windows_64_2k8_50030f55d08d5ffe6a10e76542487b1b989e4972_13_11_01_21_45_06_slow_weekly_tests_windows_64



 Comments   
Comment by Githook User [ 14/Nov/13 ]

Author:

{u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}

Message: SERVER-11573 use less data for conc_update.js
Branch: master
https://github.com/mongodb/mongo/commit/9ec9a7f6057ccaacfb915f4bca6b7ab8e8c02b13

Comment by Michael O'Brien [ 05/Nov/13 ]

Looking closer at where the actual slowness is taking place. Compare:
a slow one (115 min) http://buildlogs.mongodb.org/mci_0.9_windows_64_2k8/builds/2736/test/slow_weekly_tests_0/conc_update.js
a fast one (15 min) http://buildlogs.mongodb.org/mci_0.9_windows_64_2k8/builds/2451/test/slow_weekly_tests_0/conc_update.js

The bulk of the logging in these tests is messages like this one:

 m30201| 2013-10-24T19:58:42.051+0000 [conn1] command concurrency.$cmd command: { count: "conc", query: { x: { $lt: 3145728.0 } }, fields: {} } ntoreturn:1 keyUpdates:0 numYields:2243 locks(micros) r:159270 reslen:48 134ms

In the case of the slow test, each of those log lines are about 2-3 seconds apart.
In the case of the fast one, the difference is on the order of milliseconds.

Generated at Thu Feb 08 03:26:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.