Ticket #4773 (closed Feature Requests: worksforme)
|Reported by:||dominicstreeter@…||Owned by:||anthonyw|
|Milestone:||To Be Determined||Component:||thread|
|Keywords:||Timing Microsecond Millisecond Precision Resolution Economic Practice||Cc:||viboes|
You cannot manage a thread for a process that needs to update at once per millisecond when the resolution of waiting is this low. If a process takes 3 microseconds you can wait arbitrarily for 1.003ms.
If you expand this arbitrary method to a process that takes 0997micro seconds to complete you can spend 1.997ms running a cycle making a process run at half the speed required.
Game Logic and any process that needs to respond on the millisecond has to poll currently and only be timed to account for lag in any well written software it is good practice and economical to wait where appropriate. You can waste 0.999% of a second of energy per second per thread otherwise.