Timeline for GPU not reaching 100% usage when frame rate is dropping
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2017 at 21:28 | history | edited | trichoplax is on Codidact now | CC BY-SA 3.0 |
Remove "thanks" and add in additional thoughts that were posted as an answer
|
| Feb 14, 2017 at 17:29 | answer | added | RubyNoob | timeline score: 1 | |
| Feb 7, 2017 at 5:13 | comment | added | Gerald Lang | Hey PaulHK sorry my stack overflow account here is brand new, and something messed up with my registration so I cannot comment on my own post. Your idea that it is v-sync is an interesting one. [converted from an answer - rest of content too long for a comment moved to the question - trichoplax] | |
| Feb 7, 2017 at 3:06 | comment | added | PaulHK | Is VSync enabled? It could be the CPU is waiting for the next available frame. If the GPU takes say 20ms to complete its tasks, the CPU will wait for the next frame which would occur at ~33ms (16.6x2ms), meaning the GPU will idle for ~13ms. | |
| Feb 7, 2017 at 2:57 | review | First posts | |||
| Feb 8, 2017 at 17:35 | |||||
| Feb 7, 2017 at 2:55 | history | asked | Gerald Lang | CC BY-SA 3.0 |