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
I was looking for lightweight cross-platform sleep function that is suitable for real time applications (i.e. high resolution/high precision with reliability). Here are my findings: Scheduling Fundamentals Giving up CPU and then getting it back is expensive. According to this article, scheduler latency could be anywhere between 10-30ms on Linux. So if you need to … Read more
Use: #include <windows.h> Sleep(sometime_in_millisecs); // Note uppercase S And here’s a small example that compiles with MinGW and does what it says on the tin: #include <windows.h> #include <stdio.h> int main() { printf( “starting to sleep…\n” ); Sleep(3000); // Sleep three seconds printf(“sleep ended\n”); }
time.sleep(secs) time.sleep(secs) suspends the execution of the current thread for the given number of seconds. The argument may be a floating point number to indicate a more precise sleep time. The actual suspension time may be less than that requested because any caught signal will terminate the sleep() following execution of that signal’s catching routine. … Read more
Yes – older POSIX standards defined usleep(), so this is available on Linux: int usleep(useconds_t usec); DESCRIPTION The usleep() function suspends execution of the calling thread for (at least) usec microseconds. The sleep may be lengthened slightly by any system activity or by the time spent processing the call or by the granularity of system … Read more
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
Your thread is sharing CPU Time with other threads. The Sleep will end as soon as it is your turn again and the kernel notices the sleep time has elapsed, so it is not that accurate. CPU load, process priorities, number of concurrent threads, even from other processes, will have effect upon it.
I don’t know of any direct method to do this, but one way you could get a good idea of when it happens is to set up a setInterval task that runs, say every 2 seconds, and stores the time it last ran. Then check to see if the last time it ran is very … Read more
This will probably provide the result that you seek: -(void)textLabelChanger:(id)sender { NSString *myTextLabelString = [NSString stringWithFormat:@”%d”, gameCountDown]; textLabel.text=myTextLabelString; [self performSelector:@selector(updateTextLabelWithString:) withObject:@”sleep 5 worked” afterDelay:5.0]; [self performSelector:@selector(updateTextLabelWithString:) withObject:@”sleep 5 worked second time round” afterDelay:10.0]; } -(void)updateTextLabelWithString:(NSString*)theString { textLabel.text=theString; } There are plenty of ways to do this. Instead of having a single updateTextLabelWithString that you call … 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