You aren’t seeing anything special because there’s nothing much asynchronous work in your code. However, the main difference is that time.sleep(5) is blocking, and asyncio.sleep(5) is non-blocking. When time.sleep(5) is called, it will block the entire execution of the script and it will be put on hold, just frozen, doing nothing. But when you call … Read more
The accuracy of the time.sleep function depends on your underlying OS’s sleep accuracy. For non-realtime OS’s like a stock Windows the smallest interval you can sleep for is about 10-13ms. I have seen accurate sleeps within several milliseconds of that time when above the minimum 10-13ms. Update: Like mentioned in the docs cited below, it’s … Read more
The advantage of TimerTask is that it expresses your intention much better (i.e. code readability), and it already has the cancel() feature implemented. Note that it can be written in a shorter form as well as your own example: Timer uploadCheckerTimer = new Timer(true); uploadCheckerTimer.scheduleAtFixedRate( new TimerTask() { public void run() { NewUploadServer.getInstance().checkAndUploadFiles(); } }, … Read more
TimeUnit.SECONDS.sleep(x) will call Thread.sleep after validating that the timeout is positive. This means that as opposed to Thread.sleep, an IllegalArgumentException will not be thrown when the timeout is negative. Other than that, the only difference is readability and using TimeUnit is probably easier to understand for non-obvious durations (for example: Thread.sleep(180000) vs. TimeUnit.MINUTES.sleep(3)). For reference, … Read more
As mentioned by Outlaw Programmer, I think the solution is just to sleep for the correct number of seconds. To do this in bash, do the following: current_epoch=$(date +%s) target_epoch=$(date -d ’01/01/2010 12:00′ +%s) sleep_seconds=$(( $target_epoch – $current_epoch )) sleep $sleep_seconds To add precision down to nanoseconds (effectively more around milliseconds) use e.g. this syntax: … Read more
Yes, there’s +[NSThread sleepForTimeInterval:] (Just so you know for future questions, Objective-C is the language itself; the library of objects (one of them at least) is Cocoa.)
You should generally NOT ignore the exception. Take a look at the following paper: Don’t swallow interrupts Sometimes throwing InterruptedException is not an option, such as when a task defined by Runnable calls an interruptible method. In this case, you can’t rethrow InterruptedException, but you also do not want to do nothing. When a blocking … Read more
you always want to prevent using while loops, especially when you are forcing the code to recheck variables. It wastes CPU resources and slows down your program. I would definitely say the first one.
A wait can be “woken up” by another thread calling notify on the monitor which is being waited on whereas a sleep cannot. Also a wait (and notify) must happen in a block synchronized on the monitor object whereas sleep does not: Object mon = …; synchronized (mon) { mon.wait(); } At this point the … Read more
The sleep man page says it is declared in <unistd.h>. Synopsis: #include <unistd.h> unsigned int sleep(unsigned int seconds);