Timeline for Windows high resolution timing class
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 7, 2021 at 9:22 | vote | accept | George Tian | ||
| Mar 7, 2021 at 6:00 | history | tweeted | twitter.com/StackCodeReview/status/1368441298471038979 | ||
| Mar 7, 2021 at 1:38 | comment | added | George Tian | @Casey thanks for the tip about warming the cache, will do in the future. | |
| Mar 6, 2021 at 10:06 | answer | added | G. Sliepen | timeline score: 2 | |
| Mar 6, 2021 at 9:53 | history | edited | Toby Speight | CC BY-SA 4.0 |
Just state the problem (not the concerns) in the title
|
| Mar 6, 2021 at 4:13 | comment | added | Casey | Also, don't profile Debug builds. Make sure you're in Release mode. | |
| Mar 6, 2021 at 4:13 | comment | added | Casey | It may not be your Timer class...When you timed your functions, did you warm the cache by running the function a few million times before beginning an actual timing and avoid including output in the duration? | |
| Mar 6, 2021 at 4:07 | comment | added | Casey | Raymond Chen from Microsoft wrote up a devblog about it a couple years ago: devblogs.microsoft.com/oldnewthing/20170921-00/?p=97057 "As accurate as the hardware allows" for those particular functions | |
| Mar 6, 2021 at 3:19 | review | First posts | |||
| Mar 6, 2021 at 9:53 | |||||
| Mar 6, 2021 at 3:16 | history | asked | George Tian | CC BY-SA 4.0 |