Boost C++ Libraries: Ticket #4773: boost::this_thread::sleep(Microsecond Resolution)

type changed

viboes — Thu, 28 Oct 2010 18:03:38 GMT

type Patches → Feature Requests

Moved to Feature request as there is no patch attached.

cc set

viboes — Wed, 17 Nov 2010 20:24:49 GMT

cc viboes added

Please could you provide a test that helps to clearly identify the issue? In this way you will help the Boost community.

dominicstreeter@… — Thu, 18 Nov 2010 09:52:20 GMT

I am afraid that this ticket is somewhat redundant. The issue was I believed that microsecond timing was necessary to control millisecond interactions precisely on standard hardware.

The reason there is no microsecond timing despite the resolution being addressable now is because even windows 7 professional does not manage or support control of threading on a microsecond level. Its an inherent limitation of the way the operating system is designed. I don't imagine any OS designed for standard commercial use has this as a standard resolution because not all hardware has a high performance counter and so it would be bad practice to try and use such a counter for generic timing. I also found ways around the limitation despite being mildly less precise and efficient they work perfectly. The only real method available is a spin lock cycle.

I apologise for the confusion! In future tickets I will also provide an example application to try and explain the issue.

Thank you for your time!

viboes — Sat, 27 Nov 2010 16:15:33 GMT

I guess you are not requesting the library to use spin locks when waiting for some thing to occur. You can do it yourself.

If I've understood we can close the ticket, isn't it?

dominicstreeter@… — Sat, 27 Nov 2010 17:37:36 GMT

Yes close the ticket by all means.

status changed; resolution set

viboes — Fri, 02 Dec 2011 05:36:11 GMT

status new → closed
resolution → worksforme

See also #6195 Provide the standard time related interface using Boost.Chrono