Igor Canadi b8d23cdcb8 Revert chrono use
Summary:
For some reason, libstdc++ implements steady_clock::now() using syscall instead of VDSO optimized clock_gettime() when using glibc 2.16 and earlier. This leads to significant performance degradation for users with older glibcs. See bug reported here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59177

We observed this behavior when testing mongo on AWS hosts. Facebook hosts are unaffected since we use glibc2.17 and 2.20.

Revert "Fix timing"
This reverts commit 965d9d50b8cbb413de5e834b5b83ddbb682d0f1d.

Revert "Use chrono for timing"
This reverts commit 001ce64dc7659c65569ffb1c440e26cd23db3c94.

Test Plan: make check

Reviewers: MarkCallaghan, yhchiang, rven, meyering, sdong

Reviewed By: sdong

Subscribers: dhruba, leveldb

Differential Revision: https://reviews.facebook.net/D34371
2015-03-03 11:29:31 -08:00
..
2014-11-21 14:11:40 -08:00
2014-11-07 15:04:30 -08:00
2015-02-26 11:28:41 -08:00
2014-08-19 09:52:54 -04:00
2014-08-19 06:48:21 -07:00
2015-02-26 11:28:41 -08:00
2015-03-03 11:29:31 -08:00
2014-11-14 11:38:26 -08:00
2014-11-14 11:38:26 -08:00
2014-11-20 10:49:32 -08:00
2014-08-28 12:46:05 -04:00
2014-08-28 12:46:05 -04:00
2015-02-26 11:28:41 -08:00
2015-02-26 14:19:51 -08:00
2015-02-26 15:19:17 -08:00
2014-09-21 22:20:00 +08:00
2015-02-26 11:28:41 -08:00
2015-02-26 11:28:41 -08:00
2015-02-26 11:28:41 -08:00
2015-02-27 17:06:06 -08:00
2015-02-26 11:28:41 -08:00
2014-07-25 15:17:06 -07:00
2015-02-26 11:28:41 -08:00
2015-01-23 18:10:52 -08:00
2014-07-28 12:10:49 -07:00
2013-12-03 12:42:15 -08:00
2014-07-28 12:22:37 -07:00
2014-11-21 11:05:28 -05:00
2014-09-08 22:24:40 -07:00
2015-02-26 11:28:41 -08:00
2014-10-31 11:59:54 -07:00
2015-02-18 11:49:31 -08:00
2015-02-26 15:19:17 -08:00
2014-05-01 14:09:32 -04:00
2014-05-01 14:09:32 -04:00