summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMaxim Dounin <mdounin@mdounin.ru>2021-10-21 18:38:38 +0300
committerMaxim Dounin <mdounin@mdounin.ru>2021-10-21 18:38:38 +0300
commitf29d7ade54f8baa117f7c40fec58683952c46cdb (patch)
tree77316ee5cb8867e642d45fc835612c1d828ed275
parent1fecec0cbf1554c0473d5cca0fb55f8dc006e4ba (diff)
downloadnginx-f29d7ade54f8baa117f7c40fec58683952c46cdb.tar.gz
Removed CLOCK_MONOTONIC_COARSE support.
While clock_gettime(CLOCK_MONOTONIC_COARSE) is faster than clock_gettime(CLOCK_MONOTONIC), the latter is fast enough on Linux for practical usage, and the difference is negligible compared to other costs at each event loop iteration. On the other hand, CLOCK_MONOTONIC_COARSE causes various issues with typical CONFIG_HZ=250, notably very inaccurate limit_rate handling in some edge cases (ticket #1678) and negative difference between $request_time and $upstream_response_time (ticket #1965).
-rw-r--r--src/core/ngx_times.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/src/core/ngx_times.c b/src/core/ngx_times.c
index 7964b008f..16788c98c 100644
--- a/src/core/ngx_times.c
+++ b/src/core/ngx_times.c
@@ -200,10 +200,6 @@ ngx_monotonic_time(time_t sec, ngx_uint_t msec)
#if defined(CLOCK_MONOTONIC_FAST)
clock_gettime(CLOCK_MONOTONIC_FAST, &ts);
-
-#elif defined(CLOCK_MONOTONIC_COARSE)
- clock_gettime(CLOCK_MONOTONIC_COARSE, &ts);
-
#else
clock_gettime(CLOCK_MONOTONIC, &ts);
#endif