summaryrefslogtreecommitdiff
path: root/src/mongo/util/background_thread_clock_source_test.cpp
Commit message (Collapse)AuthorAgeFilesLines
* SERVER-41585 Modified background_thread_clock_source_test to not assume we ↵Shaileja Jain2019-06-281-1/+1
| | | | can schedule the background thread
* SERVER-39339 Remove `stdx/memory.h`ADAM David Alan Martin2019-06-101-5/+7
|
* SERVER-40166 Force BG clock now >= Date_t::lastNowJason Carey2019-03-211-67/+40
| | | | | | | | | | | | | | | | | | | | | Currently our fast clock is implemented by a background thread which wakes up every 10ms if callers continue to check it's time. If that background thread get's descheduled for a long time for some reason, this can cause the background threads time to drift substantially. If we: * force every read of date_t::now to update a new date_t::lastNow * change the background thread so that it's responsibility is to wake up and call Date_t::now() (if readers are still present) * change the background thread clock source now() to return date_t::lastNow We'll get a world in which we have the same target granularity + thread quiescence as before, but additionally ensure that even if the background thread can't be scheduled, that lastNow() will still be pushed loosely forward if there are callers of Date_t::now() elsewhere in the system. This should ensure a tighter bound on the spread between the precise and fast clock sources
* SERVER-39560 - remove leading blank line on all C++ filesBilly Donahue2019-02-131-1/+0
| | | | | | Remove leading comments that are just stating the filename. Move any file-level comments below the copyright banner. Remove leading blank lines.
* SERVER-37651 Update header files with new licenseRamon Fernandez2018-10-221-14/+16
|
* SERVER-21538 Use mockable cv wait in background_thread_clock_source_testMathias Stearn2017-03-221-31/+42
| | | | | This both makes the test run much faster and avoids spurious failures when the system scheduler decides not to run a thread for over a second.
* SERVER-21538 Put BGThreadClockSource to sleep when it isn't neededMathias Stearn2017-03-201-1/+73
| | | | | If it goes through a full granularity of sleeping without being read from, it will sleep with no timeout until the next attempt to read the clock.
* SERVER-23243 Add getPrecision to ClockSourceWaley Chen2016-04-151-18/+28
|
* SERVER-23243 Extract time-keeping from ListenerWaley Chen2016-04-151-0/+67
BackgroundThreadClockSource & FastClockSourceFactory
View Lorry Controller Status