Thread.yield() 与 Thread.sleep()的区别

最新推荐文章于 2024-09-13 15:52:34 发布

转载最新推荐文章于 2024-09-13 15:52:34 发布 · 1k 阅读

文章标签：

#thread #testing #events #mobile #up

Java 专栏收录该内容

38 篇文章

订阅专栏

本文探讨了游戏模拟器KEmulator中EventQueue重构后导致CPU使用率过高的问题，并通过对比Thread.yield()与Thread.sleep(1)的效果，发现后者能有效降低CPU使用率。在特定条件下，使用Thread.sleep(1)替代Thread.yield()可以解决内存限制引起的操作延迟。

From: http://www.j2megame.org/index.php/content/view/1608/125.html

I refactor the EventQueue in KEmulator, then test on some games.

when running MI3 and Gangstar, the CPU reached 100% utilization.

and after testing, i got my answer, cause of Thread.yield() in run() with a while(true) circle.

So i made a test, preReplace all the Thread.yield() with Thread.sleep(1) in game loading. this time, everything goes good. the MI3 got a lower 10% CPU utilization in average.

sleep() will let your thread do nothing for a certain amount of time. Basically, your thread can’t do anything until it is done sleeping.
yield() will cause your thread to voluntarily let other threads in your program run. If no other threads are ready to run, then your thread will continue.

Thread.yield() will help your thread give time to other threads, but when other threads are free or yield()ing will still take up 100% of the CPU. Otherwise, Thread.sleep() is the only way to force the CPU getting a rest.

=======================

May be there is a same case in Mobile development.

In some handset, when the game reaches the memory limit, the key events will cause an obviously delay. In Realfootball team last year, i found out that calling more Thread.yield()(two or three) in the run() circle can solve the problem.

Maybe one Thread.sleep(1) did the job here.