Related
After trying to decide which I/O scheduler to use, I decided to try running the Androbench storage performance benchmark tool for the I/O schedulers,
cfq, deadline, noop,vr and sio to find out.
All tests run on deodexed JVQ on Galaxian [email protected]
The file system used was /data (ext4)
I used standard buffer sizes (256Kb for sequential I/O) and (4kb for random I/O) To speed the tests up, I used a read file size of 16Mb and a write file size of 1Mb
I did test using the recommended sizes of 32MB and 2MB) but the rates were the same so I kept the smaller sizes to speed up the tests
I know its not very scientific but provides a rough estimate of the relative performance.
MBRS =MB/s sequential reads
MBWS =MB/s sequential writes
RRIOPS =random reads IO's/sec
RWIOPS=random writes IO's/sec
Test #1
MBRS MBWS RRIOPS RW IOPS
cfq 19.40 4.8 1014 35
deadline 19.39 6.1 1119 42
noop 19.47 9.0 1098 43
vr 17.76 7.7 1105 45
sio 18.30 6.9 1152 49
Test #2
MBRS MBWS RRIOPS RWIOPS
cfq 19.18 3.3 1057 33
deadline 26.27 5.5 1151 43
noop 19.08 8.6 1059 41
vr 19.55 6.4 1120 50
sio 19.16 6.3 1122 45
Test #3
MBRS MBWS RRIOPS RWIOPS
cfq 19.25 3.8 1120 34
deadline 18.97 7.8 1146 43
noop 19.59 9.3 1161 45
vr 19.14 6.6 1227 53
sio 19.46 7.5 1172 50
my conclusion - use NOOP or SIO(if stable)
As you can see, sequential reads (MB/s) and sequential IOPS are very high so I don't think we need to worry about these too much, as you know (from Quadrant) it's writes that are VERY slow
Unsurprisingly, we can see that the slowest scheduler is the default CFQ.
The noop scheduler produced the fastest sequential write rate on all runs.
the VR and SIO schedulers produce the greatest number of IOPS for random writes.
Think I will use the noop scheduler as it uses little CPU and is fairly well established and its not far off the random write IOPS rate.
Is someone can be arsed, I think we should test with all background processes off, using a 1Ghz speed, and run say 10 sets of tests and order the results using a spreadsheet.
Would be good to see these results run against a RFS file system too!!!
Would also be good to test I/O against say a /cache file system with journalling switched off to unserstand the actual improvement.
I am surprised at the read speed, the IO rate is equivalent to 5 or 6 15K SA/FC physical disks - Whahoo!!!!!
Hi,
Last evening I updated my kernel to Galaxian 2.0 and after reading your test results I set my I/O scheduler to noop and this morning... I found my phone hot, checked the battery status and had the nasty surprise of finding that Android OS has taken 41% of my battery and the phone didn't sleep almost all night. Did you have this problem? I'm trying to figure out whether the Android OS bug returned because of the kernel update or the I/O scheduler change.
Thanks.
Hmm, used system panel to check android and overhead for me was very low, I use juice defender and lose about 2 or 3% battery overnight, phone is cool, try wiping cache, dalvik and fix permissions and reboot once or twice, if the same change to deadline and observe difference
Sent using geek power
I am getting quite different values
Seq read 12,75 MB/s
Seq write 4.0 MB/s
Random read 1596 IOPS(4k), 6,23MB/s
Random write 41,74 IOPS(4k), 0,16 MB/s
Brotuck said:
I am getting quite different values
Seq read 12,75 MB/s
Seq write 4.0 MB/s
Random read 1596 IOPS(4k), 6,23MB/s
Random write 41,74 IOPS(4k), 0,16 MB/s
Click to expand...
Click to collapse
which scheduler you got that results?
Im going to test noop with semaphore 1.3.3
My benchmark results!
Hey, I read countless threads on I/O schedulers, but most of them were based on opinions or feelings... except this one! I want to contribute, so I decided to run my set of benchmarks too.
I used the latest AndroBench 2.0 from the market, default/recommended settings. Each I/O scheduler was tested three times, and the numbers below are the averages of the results.
Samsung Galaxy S GT-I9000
Firmware: stock 2.3.3 w/root (RSJV3, latest official firmware in Italy)
Kernel: Galaxian 2.4
File system: RFS
No overclock
Cpu governor set to "performance" to make sure frequency doesn't fluctuate during test runs.
I created a couple of simple comparison indexes:
Read Index = SeqRead * RndReadMB * RndReadIOPS
Write Index = SeqWrite * RndWriteMB * RndWriteIOPS * 100
Here are the averages. You can download the spreadsheet with all the results, it's attached to my post.
--------------noop-----vr-------sio------cfq------deadline
Read Index....57750....57305....54328....58849....60013
Write Index...31339....24051....27602....23233....18628
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My conclusion: I agree with gsw5700, NOOP is definetely the most interesting I/O scheduler for our SGS even on RFS file system. Satisfactory read speed and best-of-the-class write speed!
Here are my results (average of 3 runs)
seq.read seq.write r-read r-write
VR: 12.5 - 4.22 - 5.82 - 0.21
SIO: 12.61 - 3.86 - 6,07 - 0.207
BFQ: 12.8 - 3.93 - 6,01 - 0,18
Noop:12.6 - 4,05 - 6,03 - 0,208
(seq= sequential; r-= random; all values in MB/s)
I've heard BFS is supposedly very good, but can't find any data. Could someone run a test of it against Noop etc. so we can all see...
Thanks
Mike
Garbled meaning induced by swype when posting from XDA app on SGS I9000.
Uhm... never heard of BFS before, which kernel do you have?
ZioGTS said:
Uhm... never heard of BFS before, which kernel do you have?
Click to expand...
Click to collapse
BFS is most likely brain **** scheduler.
TalonDEV 0.4.2 0.4.3
added BFQv2-r1 I/O Scheduler (SIO default)
BFS is a CPU scheduler which has nothing to do with Noop,sio,vr,cfq which are i/o schedulers
A BFQ test is a few posts up....
.:Crack:. said:
Here are my results (average of 3 runs)
seq.read seq.write r-read r-write
VR: 12.5 - 4.22 - 5.82 - 0.21
SIO: 12.61 - 3.86 - 6,07 - 0.207
BFQ: 12.8 - 3.93 - 6,01 - 0,18
Noop:12.6 - 4,05 - 6,03 - 0,208
(seq= sequential; r-= random; all values in MB/s)
Click to expand...
Click to collapse
I did another test with BFQ and noop (5 runs each) and noop won.
(BTW i was a V(R) fanboy before )
.:Crack:. said:
BFS is a CPU scheduler which has nothing to do with Noop,sio,vr,cfq which are i/o schedulers
A BFQ test is a few posts up....
Click to expand...
Click to collapse
Whoops! Sometimes a little bit of knowledge makes me dangerous!... But this time I got away with just looking silly!!!
Thanks for correcting me... making mistakes its often the best way to learn!
Mike
Garbled meaning induced by swype when posting from XDA app on SGS I9000.
Interesting test, however I am troubled with my results. I tried running this Androbench software and it seems that I have a lot of fluctuations.
For example during one test I get 4.92mb/s write speed @ noop and then during second test I get 1.52mb/s write speed @ noop test and last one was 2.02mb/s. I mean write speed is write speed you can have minor fluctuations say 4.92mb/s on the first run and 4.90 on the second run. This is of course while the device was not used.
If I run a benchmark software on my pc, I will get almost all the time identical results.
So either there is something wrong with teh software or something else is at play.
Also this guy from over here: http://www.team-continuum.net/home/index.php?topic=290.0 claims that operating on different CPU governors also has impact on benchmark results.
Theoretically, SIO is the best.
Benchmark can't represent real life situations as I/O transactions are mostly spurious rather than 1 big chunk of data to and fro (on which this is what benchmarks are doing).
More info at my sig (Android Optimization Tips). CTRL-F for scheduler.
What does the phone do most of, i guess it reads much more than it writes so wouldn't it be better to use a fast reading with satisfactory write speeds scheduler?
bobdoblo said:
What does the phone do most of, i guess it reads much more than it writes so wouldn't it be better to use a fast reading with satisfactory write speeds scheduler?
Click to expand...
Click to collapse
+1
and what about the row sceduler
row supposed to be the best fro read, its designed for read or im mistaken?
herc2k said:
+1
and what about the row sceduler
row supposed to be the best fro read, its designed for read or im mistaken?
Click to expand...
Click to collapse
...I ran some tests for schedulers, including row and for the test the row seems to be the best, I'm using it on JB 4.2...
What about the Zen and Row I/O schedulers?
The Scheduler is an algorithm that, given a set of requests for access to a resource, establishing a temporal order for the execution of such requests, favoring those that meet certain criteria in order to optimize access to that resource.
The difference between the various scheduler is the focus on certain criteria rather than on others.
The choice of a given scheduler does not produce visible changes so as to the choice of the governor, but still provides some improvements.
As usual schedulers are personally tested to find one that best suits your needs.
DEADLINE
It aims to provide a deadline, a deadline for all requests in order to avoid undesirable phenomena such as the "starvation" or the eternal waiting for some requests that occurs when one or more background processes are left indefinitely in the queue the ready, because there is always at least one of the highest priority ready process.
VR
The next request is performed according to the distance from the last request. In the network running good opinions about this scheduler.
NOOP
Push all requests in a single queue simply by their arrival order, grouping together those contiguous.
SIO
E 'the scheduler simpler, does not make any type of sort, is intended only for the purpose of obtaining a low-latency, ie to reduce the amount of time that elapses between the instant at which the request is generated and that in which the request is satisfied.
CFQ
Order requests of different processes in queues for each queue type and assigns a specific interval of time whose duration depends on the priorities assigned to processes. Can be considered the Ondemand the scheduler, the scheduler is in fact more balanced, doing its job in an honest manner.
BFQ
It 's based on CFQ but, instead of the intervals of time, assigns a part of the bandwidth of the disc to each process running in a proportional manner.
Anticipatory
Order requests based on criteria predictive, that puts the demands paused for a short period of time in anticipation that more of this to come to aggregate them.
ADAPTIVE ANTICIPATORY SCHEDULER
For the anticipatory scheduler, we scale up the anticipation timeout (antic expire) using the latency scaling factor over time. When the virtual disk latencies are low a small scaling of the timeout is sucient to prevent deceptive idleness, whereas when the latencies are high a larger scaling of the timeout value may be required to achieve the same. Note that such dynamic setting of the timeout value ensures that we attain a good trade-o between throughput (lost due to idling) and deceptive idleness mitigation. Setting a high value for the scaling factor (increasing idling time) only happens when the disk service latencies themselves are higher. This may not necessarily cause a signicant loss in throughput, because submitting a request from another process instead of idling is not going to improve throughput if the virtual disk itself does not get any faster than it is at the current period. A higher anticipation timeout might also be capable of absorbing process scheduling eects inside the VM. The results for the adaptive anticipatory scheduler are shown in Figure 2. The read time with our modied implementation (third bar in the dierent scheduler combinations) shows that it is possible to mitigate the eects of deceptive idleness by adapting the timeout. An interesting related observation is that the level to which the improve- ment is possible varies for dierent Domain-0 schedulers; noop - 39%, anticipatory - 67% and cfq - 36%. This again points to the fact that the I/O scheduler used in Domain-0 is important for the VM's ability in enforcing I/O scheduling guarantees. Dierent Domain-0 I/O schedulers likely have a dierent service latency footprint inside the VMs, contributing to dierent levels of improvement.
FIOS
Flash-based solid-state drives (SSDs) have the potential to eliminate the I/O bottlenecks in data-intensive applications However the large performance discrepancy between Flash reads and writes introduces challenges for fair resource usage. Further, existing fair queuing and quanta-based I/O schedulers poorly manage the I/O anticipation for Flash I/O fairness and efficiency. Some also suppress the I/O parallelism which causes substantial performance degradation on Flash. This paper develops FIOS, a new Flash I/O scheduler that attains fairness and high efficiency at the same time. FIOS employs a fair I/O time-slice management with mechanisms for read preference, parallelism, and fairness-oriented I/O anticipation. Evaluation demonstrates that FIOS achieves substantially better fairness and efficiency compared to the Linux CFQ scheduler, the SFQ(D) fair queuing scheduler, and the Argon quanta-based scheduler on several Flash-based storage devices (including a CompactFlash card in a low-power wimpy node). In particular, FIOS reduces the worst-case slowdown bya factor of 2.3 or more when the read-only SPECweb workload runs together with the write-intensive TPC
ROW
Row stands for READ Over WRITE which is the main requests dispatch policy of this algorithm. The ROW IO scheduler was developed with the mobile devices needs in mind. In mobile devices we favor user experience upon everything else, thus we want to give READ IO requests as much priority as possible. In mobile devices we won't have as much parallel threads as on desktops. Usually it's a single thread or at most 2 simultaneous working threads for read & write. Favoring READ requests over WRITEs decreases the READ latency greatly.
The main idea of the ROW scheduling policy is: If there are READ requests in pipe - dispatch them but don't starve the WRITE requests too much. Bellow you'll find a small comparison of ROW to existing schedulers. The test that was run for these measurements is parallel read and write.
Which scheduler is the most stable with decent battery & performance with smartassv2?
danshuynh said:
Which scheduler is the most stable with decent battery & performance with smartassv2?
Click to expand...
Click to collapse
Hello, I am very happy with smartass v2, and CFQ scheduler.
good performance and excellent battery
Another great Stempox guide. Thanks :good:
jayjay3333 said:
Another great Stempox guide. Thanks :good:
Click to expand...
Click to collapse
yes friend, thank you
Thank you! Awesome guides btw, especially for noobs like me
danshuynh said:
Thank you! Awesome guides btw, especially for noobs like me
Click to expand...
Click to collapse
thanks, is a pleasure to help new guys if possible
all about I/O SCHEDULERS
http://forum.xda-developers.com/showpost.php?p=22134559&postcount=4
If you want you can post as governor-scheduler combination frequently used and why.
would be useful
goverrnor: lulzactive
IO: sio
for battery and performance..
kernel matrix ics.. oc 1300mhz,bus speed default..
I've almost always used On Demand / Deadline.
To be honest, I've tried other combos, but I've never really noticed much difference either way. On Demand / Deadline is the default for my current kernel.
Thanks
Thank you sir,
Thanks for the summary!
bedalus said:
Thanks for the summary!
Click to expand...
Click to collapse
I still use the default cfq
soon update the thread with description new i / o scheduler
Can someone shed more light on smartassv2 i/o scheduler ?
Btw I thank the threadstarter for this informative thread ..
snoopnoob said:
Can someone shed more light on smartassv2 i/o scheduler ?
Btw I thank the threadstarter for this informative thread ..
Click to expand...
Click to collapse
hi, smartassv2 is a governor, and the description you can find it here: http://forum.xda-developers.com/showthread.php?t=1767797
Found this about the ZEN scheduler,
Q: What is the zen I/O scheduler?
A: Well, the question that was asked above led me to an analysis of V(R ), deadline, and some others. I already knew, but realized "this is the main feature of V(R), but wait it has no benefit to us smartphone users." So I thought about adjusting the way V(R ) handled requests and how it dispatched them (I chose V(R ) because i'd rather not tinker with a scheduler thats official and widely supported). Then I was looking over it, and realized I might as well just write a new one I don't need any of this stuff. So I came up with something awfully similar to SIO, although its a bit simpler than SIO (closer to no-op) and works just slightly different.
- It's an FCFS (First come, first serve) based algorithm. It's not strictly FIFO. It does not do any sorting. It uses deadlines for fairness, and treats synchronous requests with priority over asynchronous ones. Other than that, pretty much the same as no-op.
Click to expand...
Click to collapse
stempox said:
hi, smartassv2 is a governor, and the description you can find it here: http://forum.xda-developers.com/showthread.php?t=1767797
Click to expand...
Click to collapse
Thank for the link dude ...
OP update.
Hi guys, in my opinion i/o performance is just bad... ? how i can improve it?? I join screen from androbench
Use L Speed app it has an section for io performance
You may also try to disable fsync...
FOR DEVS AND USERS BEFORE FIGHT ME CLICK HERE!: https://forum.xda-developers.com/showpost.php?p=70362424&postcount=3
Code:
DISCLAIMER!!
I am not responsible in any way for anything that can be happen to your device when you flashing my kernels.You do so at your own risk!
Features
Anykernel:
- Anykernel2 zip for maximum compatibility with all ROMs, CrazyAquaKernel uses your existing ramdisk (Do NOT flash this over other custom kernels!You should only flash CrazyAquaKernel over the kernel that came with your ROM!!)
Toolchain:
UBERTC 4.9 Toolchain
CPU:
- governors:
crazyactive(my governor:balance governor for great battery life and performance based on interactive)
interactive
impulse
ondemand
smartmax
zzmoove
ondemandplus
pegasusq
nightmare
conservative
lionheart
powersave
userspace
yankactive
smartmax_eps
intellidemand
intelliactive
- MSM Limiter
- state notifier
IO schedulers:
bfq
tripndroid
cfq
noop
deadline
fiops
row
sio
zen
vr
fifo
TCP congestion controls:
cubic
bic
westwood
htcp
highspeed
hybla
reno
bic
hybla
vegas
lp
yeah
illinois
scalable
- tcp congestion changed to Westwood
GPU:
- governors:
msm-adreno-tz
simple_ondemand
powersave,performance
userspace
cpubw_hwmon
msm_cpufreq
- Adreno idler
- simple gpu algorithm
Thermal control:
- Intelli thermal v2
Hotplug:
- Disabled MP Decision hotplug
- Enabled Bricked Hotplug
- Prevent wakelock when ambiend display disabled(misc control tab)
Sound:
- Faux sound updated and fixed
More:
- Kernel runs with SELinux permissive by default
- init.d support
- insecure kernel (adb has root privileges)
- fast charge
- cpu voltage control
- pvs level info
- Kcal v2
- Frandom support
- Disabled Arch Power
- CRC Check Disabled
- Gentle Fair Sleepers (Disabled by default)
- Enabled All Suspend and Idle Modes
- Power Suspend Mode/State
- Dynamic filesystem read-ahead
- A lot improvments
- A lot fixes
Download Link CrazySuperKernel [AnyKernel]:https://www.androidfilehost.com/?fid=889764386195923630
Installation guide
Do NOT flash this over other custom kernels!
You should only flash CrazyAquaKernel over the kernel that came with your ROM!!
- Download Kernel from this thread
- Flash it with Recovery
[Wipe cache and Dalvik cache recommended]
- Then Reboot
Enjoy the CrazyAquaKernel !!!!
Credits
thx Showp1984
thx Faux123
thx Savoca
thx RenderBroken
thx Neobuddy
thx Myfluxi
thx FranciscoFranco
thx SultanXDA
thx osm0sis
thx ShinyShide
thx bhb27
thx Lord Boeffla
thx yank555
thx apb_axel
thx the devs where made the cm14 bootable and working
thx CrazyGamerGR yeh me
XDA:DevDB Information
CrazyAquaKernel, Kernel for the OnePlus X
Contributors
CrazyGamerGR
Source Code: https://github.com/CrazyGamerGR/CrazyAquaKernel-opx-los
Kernel Special Features:
Version Information
Status: Beta
Created 2017-08-18
Last Updated 2017-08-17
FAQ
Recommended app : Kernel Adiutor
changelogs
v1.0/18-08-17
- initial release
If u use zzmove governor disable all the hotplugs coz it use its own hotplug as anyone knows.
[Q]How i select profile from kernel tweaker app?
[A]You need to go in governor tunable-profile number and select the number of the profile from the list.
Zzmove profiles
1 ) Default -> will set governor defaults
2 )ybat -> Yank Battery -> a very good battery/performance balanced setting - DEV-NOTE: highly recommended!
3 )ybatext-> Yank Battery Extreme -> like yank battery but focus on battery saving
4 )zzbat-> ZaneZam Battery -> a more 'harsh' setting strictly focused on battery saving - DEV-NOTE: might give some lags!
5 )zzbatp -> ZaneZam Battery Plus -> NEW! reworked faster battery setting - DEV-NOTE: recommended too!
6 )zzopt -> ZaneZam Optimized -> balanced setting with no focus in any direction - DEV-NOTE: relict from back in the days, even though some people still like it!
7 )zzmod -> ZaneZam Moderate -> NEW! setting based on 'zzopt' which has mainly (but not strictly only!) 2 cores online
8 )zzperf -> ZaneZam Performance -> all you can get from zzmoove in terms of performance but still has the fast - down scaling/hotplugging behaving
9 )zzinz-> ZaneZam InZane -> NEW! based on performance with new insane scaling active. a new experience!
10 )zzgame-> ZaneZam Gaming -> NEW! based on performance with scaling block enabled to avoid cpu overheating during gameplay
reserve1
reserve2
Checking this out. So far on Purenexus it seems pretty good. Nice and responsive on default settings (Crazy governor selected)
Tanner1294 said:
Checking this out. So far on Purenexus it seems pretty good. Nice and responsive on default settings (Crazy governor selected)
Click to expand...
Click to collapse
Cool m8,thx for feedback
Sent from my iPhone using Tapatalk Pro
really good eliminated 90% of scroll issue in some apps when using ondemand governor in cpu/gpu settings.
psychem said:
really good eliminated 90% of scroll issue in some apps when using ondemand governor in cpu/gpu settings.
Click to expand...
Click to collapse
Thx for feedback m8
Sent from my iPhone using Tapatalk Pro
Can u add an option for 27mhz gpu
psychem said:
Can u add an option for 27mhz gpu
Click to expand...
Click to collapse
Sure,i had it in some of my kernels but i removed it
Sent from my iPhone using Tapatalk Pro
There's only one thing I've noticed that I would change, the cpu voltages by default are noticeably higher than stock (which on my personal device is still too high).
---------- Post added at 05:48 PM ---------- Previous post was at 05:28 PM ----------
Also if intelithermal is active at all it seems to lock the max frequency to 1700mhz no matter what settings are chosen.
Tanner1294 said:
There's only one thing I've noticed that I would change, the cpu voltages by default are noticeably higher than stock (which on my personal device is still too high).
---------- Post added at 05:48 PM ---------- Previous post was at 05:28 PM ----------
Also if intelithermal is active at all it seems to lock the max frequency to 1700mhz no matter what settings are chosen.
Click to expand...
Click to collapse
Yeh its for lower temperatures m8
Sent from my iPhone using Tapatalk Pro
CrazyGamerGR said:
Yeh its for lower temperatures m8
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
I'm saying if you set the temperatures to 80C it will throttle the cpu when it's at 50C. It doesn't function correctly.
Tanner1294 said:
I'm saying if you set the temperatures to 80C it will throttle the cpu when it's at 50C. It doesn't function correctly.
Click to expand...
Click to collapse
I will check it m8
Sent from my iPhone using Tapatalk Pro
Nice Kernel seems good.
But i think some fundamental things are missing, like usb fast charge, and can you add elementalx governor???
Thx
Fjss said:
Nice Kernel seems good.
But i think some fundamental things are missing, like usb fast charge, and can you add elementalx governor???
Thx
Click to expand...
Click to collapse
Maybe soon m8
Sent from my iPhone using Tapatalk Pro
it upport cm13?
LolHacker17 said:
it upport cm13?
Click to expand...
Click to collapse
Yes, it does upport cm13. LOS and CM came from the same sources.
Can i use it om resurrection remix 7.1.2??
Share your experience about ROMs of MI 9T ..
Which one do you use now and which one is your favorite and why?
It will help others to switch like me ?
Thank you in advance ?
I am too curious, as I've just bought a Mi 9T and haven't decided yet which ROM I'll try 1st !
From what I'm seeing, the options are MANY:
- LineageOS
- HavocOS
- AOSPExtended
- ExtendedUI
- Evolution X
- Pixel Experience
- Paranoid Android Quartz Alpha
- ....
- ....
I'm familiar already with LineageOS and AOSPExtended (with another device), both are REALLY good...
But from what i am reading, the most Feature Rich / Customizable of all is HavocOS ?
The best ROM to me, and the best customizable is MSM Xtended 6.0 with Anxiety as I/O Scheduler.
https://forum.xda-developers.com/mi-9t/development/rom-msm-xtended-project-v6-0-t4052911
Its customisation level is far beyond Havoc's 3.2, Lineage 17.1, AOSP Extended 7.0 and AOSip Quiche.
Lermite said:
MSM Xtended 6.0
Click to expand...
Click to collapse
SOLD !!!!!!
indeed, it has so many features I'm seriously considering abandoning Xposed for good!
I stopped reading at:
Code:
[B]- System[/B]
Sensor block per-package
Smart Pixel
Wakelock blocker
Amazing !!! :highfive::victory::laugh:
can't wait to flash it clean!
Lermite said:
The best ROM to me, and the best customizable is MSM Xtended 6.0 with Anxiety as I/O Scheduler.
https://forum.xda-developers.com/mi-9t/development/rom-msm-xtended-project-v6-0-t4052911
Its customisation level is far beyond Havoc's 3.2, Lineage 17.1, AOSP Extended 7.0 and AOSip Quiche.
Click to expand...
Click to collapse
I am curently using this ROM from 3 weeks.
What are the benefits of using Anxiety as I/O Scheduler?
Wich is the default? And how to change to the one you are using?
Octavian87 said:
I am curently using this ROM from 3 weeks.
What are the benefits of using Anxiety as I/O Scheduler?
Wich is the default? And how to change to the one you are using?
Click to expand...
Click to collapse
The customisation level of this rom is stunning but it isn't the smoothest.
According to the Aututu benchmark, this rom sucks during a specific test: "ROM random access" that gives only 4600 with the default I/O scheduler CFQ.
Setting Anxiety instead increases this score to more than 10000. This is like unleashing the rom.
My experience of the impact of this score to the everyday use come from my previous phone, the Redmi Note 5, much less powerful than the Mi 9T.
With this score at 1700, browsing a long list was laggy as hell, a real pain to the user.
With this score at 7000, browsing the same list was smooth.
That's why tweaking the I/O scheduler to boost the result to this benchmark test is useful, not only to get a higher score.
The scheduler can be set through any kernel tweaking app.
I use Smartpack Kernel Manager, but it isn't the only one.
Lermite said:
The customisation level of this rom is stunning but it isn't the smoothest.
According to the Aututu benchmark, this rom sucks during a specific test: "ROM random access" that gives only 4600 with the default I/O scheduler CFQ.
Setting Anxiety instead increases this score to more than 10000. This is like unleashing the rom.
My experience of the impact of this score to the everyday use come from my previous phone, the Redmi Note 5, much less powerful than the Mi 9T.
With this score at 1700, browsing a long list was laggy as hell, a real pain to the user.
With this score at 7000, browsing the same list was smooth.
That's why tweaking the I/O scheduler to boost the result to this benchmark test is useful, not only to get a higher score.
The scheduler can be set through any kernel tweaking app.
I use Smartpack Kernel Manager, but it isn't the only one.
Click to expand...
Click to collapse
I get now in antutu 11000 score for rom random acces with the default setting
My bad. I have many apps installed and perhaps one of them has waken up to do its business during the benchmark.
This bunch of apps also explains my score stays lower than yours.
I have to do these tests again to evaluate with more reliability the gain of the I/O scheduler Anxiety in place of CFQ.
Anyway, the MSM Xtended is the best rom for the Mi 9T regardless the benchmarks scores.
EDIT: I confirm I have to apologies. I've no clue what went wrong during my previous tests because the new ones gives different results.
They show that changing the I/O scheduler is pointless.
Here are my results with CFQ then Anxiety:
I'm getting 267000 points. Is ok. Any other settings we cand do for better perfomance and battery?
I've found why I've gotten only 4600 to the Rom Random Access Antutu test while the actual score is 11000:
I got the low score from MSM Xtended 6.0, but an earlier version that had another kernel the actual from 2020-02-17.
That means this score depends much more on the kernel than the rom.
I'm on MSM, tried Kernel Adiutor or Smarpack kernel manager.
When kernel manager started, CPU minimum frequency is forced to be 1.2GHz and no lower, even with CPU section untouched.
Without kernel manager, it can get as low as about 600MHz. So I gave up changing scheduler.
But anyway MSM is best rom as it is. It is more customizable than even havoc.
edit
I tried again and saw CPU frequency going down. Now let's see the scheduler.
I'm using msm extended as well but I'm having issues with Netflix, same for you guys? I get the 5.7 error. There is this magisk tweak but it reduces widevine to l3