Windows: GetTickCount has too low timer resolution

[pps83]

GetTickCount does not necessarily have good precision if somebody tries to debug/analyze timings. It could have 1 or even 10 ms precision.
Would it be acceptable to submit a patch that adds a CURL option that sets TIMER FUNCTION that would be used to retrieve timestamps instead?

Alternatively it could simply use QueryPerformanceCounter/QueryPerformanceFrequency on windows.

curl/lib/timeval.c

Line 38 in 27a5e1f

DWORD milliseconds = GetTickCount();

[bagder]

option that sets TIMER FUNCTION that would be used to retrieve timestamps instead?

That would imply that some users would want different timestamps. I've never heard of such users.

Alternatively it could simply use ...

I think it would be good enough if we just used the best available high resolution timer by default.

[pps83]

I think it would be good enough if we just used the best available high resolution timer by default.

See proposed fix: timeval: use QueryPerformanceCounter on Windows #3318