mirror of
https://github.com/curl/curl.git
synced 2026-04-14 13:01:42 +08:00
2de22a00c7
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 |
||
|---|---|---|
| .. | ||
| BUFQ.md | ||
| BUFREF.md | ||
| CHECKSRC.md | ||
| CLIENT-READERS.md | ||
| CLIENT-WRITERS.md | ||
| CODE_STYLE.md | ||
| CONNECTION-FILTERS.md | ||
| CURLX.md | ||
| DYNBUF.md | ||
| HASH.md | ||
| LLIST.md | ||
| MID.md | ||
| MQTT.md | ||
| MULTI-EV.md | ||
| NEW-PROTOCOL.md | ||
| PORTING.md | ||
| RATELIMITS.md | ||
| README.md | ||
| SCORECARD.md | ||
| SPLAY.md | ||
| STRPARSE.md | ||
| TIME-KEEPING.md | ||
| TLS-SESSIONS.md | ||
| UINT_SETS.md | ||
| WEBSOCKET.md | ||
Internals
This directory contains documentation covering libcurl internals; APIs and concepts that are useful for contributors and maintainers.
Public APIs are documented in the public documentation, not here.