| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Android Support Forum
Thread: Performance difference in big.LITTLE cores |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
fuzzydice555
Advanced Cruncher Joined: Mar 25, 2015 Post Count: 89 Status: Offline Project Badges: 
|
Hello All!
----------------------------------------I recently got my hands on a few used Odroid XU4 and Rock Pi 4 machines. Both of those are big.LITTLE designs, with some cores built for efficiency, some for performance. However, when I check the results, there is no major difference between runtimes between tasks. All machines are running on 100% CPU, in BoincTasks I see there are indeed the max 6 / 8 tasks running concurrently. What could be the reason that I see no short runtime tasks (big core) vs long runtime (little cores) tasks? I have two guesses: - Maybe the scheduler is actually rotating tasks between cores, so a single task has some runtime on big and some runtime on a little core? - Or the difference between big & little cores is not significant enough to show up in statistics?  |
||
|
|
PMH_UK
Veteran Cruncher UK Joined: Apr 26, 2007 Post Count: 765 Status: Recently Active Project Badges: 
|
Windows and Linux appear to rotate between cores so likely Android does too.
----------------------------------------I found some tasks sometimes slowed until I locked some/all tasks to a core/thread. Paul.
Paul.
|
||
|
|
Acibant
Advanced Cruncher USA Joined: Apr 15, 2020 Post Count: 126 Status: Offline Project Badges:
|
The only performance difference I see on my Odroid N2+ units is between different MCM tasks that use one of two algorithms. So I would agree that tasks are getting rotated between cores.
---------------------------------------- |
||
|
|
|