mirror of
https://github.com/curl/curl.git
synced 2026-08-24 14:13:32 +03:00
lib: keep timestamp in easy handle
Use `data->progress.now` as the timestamp of proecssing a transfer. Update it on significant events and refrain from calling `curlx_now()` in many places. The problem this addresses is a) calling curlx_now() has costs, depending on platform. Calling it every time results in 25% increase `./runtest` duration on macOS. b) we used to pass a `struct curltime *` around to save on calls, but when some method directly use `curx_now()` and some use the passed pointer, the transfer experienes non-linear time. This results in timeline checks to report events in the wrong order. By keeping a timestamp in the easy handle and updating it there, no longer invoking `curlx_now()` in the "lower" methods, the transfer can observer a steady clock progression. Add documentation in docs/internals/TIME-KEEPING.md Reported-by: Viktor Szakats Fixes #19935 Closes #19961
This commit is contained in:
parent
425a2aa1af
commit
2de22a00c7
67 changed files with 598 additions and 458 deletions
|
|
@ -2813,7 +2813,8 @@ static CURLcode setopt_offt(struct Curl_easy *data, CURLoption option,
|
|||
if(offt < 0)
|
||||
return CURLE_BAD_FUNCTION_ARGUMENT;
|
||||
s->max_send_speed = offt;
|
||||
Curl_rlimit_init(&data->progress.ul.rlimit, offt, offt, curlx_now());
|
||||
Curl_rlimit_init(&data->progress.ul.rlimit, offt, offt,
|
||||
&data->progress.now);
|
||||
break;
|
||||
case CURLOPT_MAX_RECV_SPEED_LARGE:
|
||||
/*
|
||||
|
|
@ -2823,7 +2824,8 @@ static CURLcode setopt_offt(struct Curl_easy *data, CURLoption option,
|
|||
if(offt < 0)
|
||||
return CURLE_BAD_FUNCTION_ARGUMENT;
|
||||
s->max_recv_speed = offt;
|
||||
Curl_rlimit_init(&data->progress.dl.rlimit, offt, offt, curlx_now());
|
||||
Curl_rlimit_init(&data->progress.dl.rlimit, offt, offt,
|
||||
&data->progress.now);
|
||||
break;
|
||||
case CURLOPT_RESUME_FROM_LARGE:
|
||||
/*
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue