1600Mhz on opi

[Melanrz]

Can i change cpu max frequency to 1600Mhz like on loboris img? only for testing purpose.Or is locked witch kernel compilation??

[tkaiser]

With loboris' settings 1600 were never possible. It's just about unlocking 1536 MHz (240 MHz more than the maximum clockspeed now). And no one have ever tested whether H3 works reliable at this clockspeed/voltage since this would require running these tests: http://linux-sunxi.org/Hardware_Reliability_Tests#CPU

 

And since these settings would require insane overvolting and in reality the speed gains aren't existing the whole approach is pretty useless. But you can try it anyway, just use a script.bin for OPi PC and give it a try. And please keep in mind that with loboris' settings at certain sane clockspeeds H3 will be undervolted (stability issues) and at the upper ones the SoC is overvolted (heat and longevity problems).

 

And you should also use RPi-Monitor to get the idea what happens in reality (without a fan H3 will be slower than with our settings since throttling will occur more early)

[Melanrz]

Thanks for answer i take a look for this,i will try only for how much gain more power on emulators,but only test,no normal run.Your armbian settings is stable and comfortable for os.

[Toast]

Overclocking often leads to instability seen it over and over on OSMC better to run at normal then overclocked.

[tkaiser]

Overclocking often leads to instability

 

The more important point is: Unless you don't understand what you're doing overclocking leads easily to less performance.

 

It's about stability/reliability when you increase clock speeds. Then you have to also adjust VDD_CPUX (the core voltage the CPU cores are fed with) and then temperatures increase and if throttling is implemented by a brute-force overclocking attempt you end up with a slower system since higher voltages leading to more heat emissions leading to earlier throttling leading to a slower system.

 

As a side note: I've never seen any overclocker interested in this realibility stuff. Most of them are even that moronic to not even take care about throttling and simply have fun frying their boards at high clockspeeds/voltages being totally idle all the time.

 

When we developed the THS settings for Pine64 we got a huge gain in real world performance by allowing more and not higher cpufreq operating points since now throttling happened more fine grained, allowing the CPU cores not only to jump between eg. 816 and 1008 MHz but also use intermediate frequencies: https://github.com/longsleep/build-pine64-image/pull/3#issuecomment-194980231 (this is a nice read when you want to really dig into).

 

The settings used in Orange Pi forums last year (loboris) were rather bad since they made use of just 2 DVFS operating points and not that much available clockspeeds to jump between: http://linux-sunxi.org/User:Tkaiser#Lessons_to_learn_from_Xunlong (I speak about Xunlong there all the time but in fact Xunlong's original settings were different and this were actually loboris' settings). So unless you used an annoying fan on top of a heatsink your board always performed slower compared to Armbian settings now. And that's maybe the most funny thing: You get a faster board staying more cool just by trying to understand the relationship between clockspeed, VDD_CPUX voltage, temperatures and configured throttling behaviour. You get more performance by refraining from overclocking/overvolting.

 

And loboris' settings had another flaw: Since he used only 2 DVFS operating points at specific clockspeeds (1.2 GHz) his settings lead even to undervoltage which might cause stability problems.

 

So while it's possible to increase our max. clockspeed from 1296 MHz to 1536 MHz this would only make sense when used together with both heatsink and fan and with really CPU bound workloads that keep all 4 CPU cores all the time at 100%. Otherwise it's simply not worth the efforts. And 100% CPU load all the time is a clear sign that you chose the wrong board. Since numbercrunching on a H3 is plain silly and all the stuff that needs high performance is done on other parts of the SoC way more efficiently:

• 2D/3D GPU acceleration for games -- works now on Mali400 and with next Armbian release you will see a performance increase by 1.5 - 2
• HW accelerated video decoding: works now, playing HEVC/1080p with high bitrates consumption increases by 0.8W max, temperatures by 6-8°C and cpufreq doesn't matter at all

So this whole SBC overclocking is pretty useless anyway. Sane THS settings and the use case in question (who wants an annoying fan?) and intelligent settings in the distro itself are way more important.

 

BTW: Too funny: The original THS settings Xunlong used can be seen here. They were responsible for slow H3 boards that got even slower when running demanding tasks since then CPU cores got killed pretty fast. We developed sane settings, the whole story has been discussed endlessly. And guess what: Now that SinoVoip starts with their Orange Pi clone BPi M2+ they chose to rely on exactly the SAME moronic THS settings leading to really bad benchmark scores for their Banana Pi M2+ when used with their settings (Armbian is not affected, I adjusted throttling settings for BP2 M2+ accordingly and even added a special corekeeper service for BPi M2+ so using BPi M2+ with Armbian or SinoVoip images might make a difference of more than 400% when we're talking about CPU performance).

[Melanrz]

Thanks for explaining this question,with settings on Armbian desktop work very well,stable and fluid,and cpu usage same to by on normal level.