Im currently running latest omgb with chads ingenious beta while using no frills cpu app. Is it better to run the stock bfq or use noop considering noop is for flash based devices?
No-op has to be the worst of all option. It's so bad, not even HTC uses it in their stock kernels. Deadline is FAR more optimized for MMC drives and devices. BFQ, depending on what you do with your device, may be quicker, may not be. CFQ isn't bad of AOSP, but displays noticeable lag on many Sense ROMs. VR.... well, good luck finding info on that one. Personally, I would stick with either BFQ or Deadline.
giving deadline a shot and seems smoother
Rock n roll. Glad to hear.
Related
I was wondering what the best i/o scheduler is for our device? I see everyone in DEV recommending us to use CFQ but is there any noticeable difference between any of the other i/o schedulers such as noop anticipatory and deadline?
And if anyone could point me towards somewhere where I could read and understand a bit about what an i/o scheduler is exactly...that'd be awesome. Thanks!
I have read that noop is good to use. I believe I also read that BFQ yields the best performance but only some kernels have that option.
Sent from my SPH-D700 using XDA Premium App
I have always used cfq, but its because im a linux guy.. ive recently been guided to look into noop, and i believe that it is the best for solid state or flash devices, because it leaves the performance optimization to the storage subsystem (xsr). not wasting resources doing double work.. flash drives dont need data grouped together close on a platter like physical disk to reduce seek time..
EDIT: BFQ is like an enhanced CFQ, and thanks to decad3nce for pointing me to look more into NOOP
Where does that leave deadline? I always see it as an option
Sent from my SPH-D700 using XDA Premium App
deadline is mainly used in database application servers.. it basically means each read or write transaction has a deadline.. usually 400ms on a read, and 3-5s on a write. best for high performance platter disc, and it queues the reads and writes, not really practical for a workstation, or a phone. definately not a good idea for a battery operated device imo, even with a journal, because a 3-5 sec queued write, even with a journal, which still has a commit time after that, you could lose data even with a journal.
JohnCorleone said:
I have read that noop is good to use. I believe I also read that BFQ yields the best performance but only some kernels have that option.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I'm using the Genocide Kernel, and latest voltage control app, but it seems to not have BFQ as an option, so I'll give noop a try. Thanks
HI everyone. i have yet another question! lol.
i tried looking on google but noting specific for the epic. i was curious what the best cpu governor and the i/o scheduler is.
for the schedulers i have noop, cfq, bfq, deadline and sio
for cpu governors i have interactive, interactive x, ondemand, smartass, smartass v2 userspace, performance, conservative and powersave.
I use SmartassV2 and noop. SmartassV2, in my opinion, keeps the CPU frequencies low unless the power is really needed. Ondemand works well, but it is a little to generous some times. I use noop because it works well with flash memory. I am going to try out deadline because it seems like it would allow apps to load faster.
Just a quick FYI...
The SIO scheduler is supposed to be based on noop and deadline.
I haven't done much testing with it, but it specifically says it's designed for flash devices.
=]
nubecoder said:
Just a quick FYI...
The SIO scheduler is supposed to be based on noop and deadline.
I haven't done much testing with it, but it specifically says it's designed for flash devices.
=]
Click to expand...
Click to collapse
I was doing some testing with Quadrant and SIO gets the highest score. I am going to try it out this week and see how it is in the long run. Thanks for the heads up nube.
Gavisann said:
I was doing some testing with Quadrant and SIO gets the highest score. I am going to try it out this week and see how it is in the long run. Thanks for the heads up nube.
Click to expand...
Click to collapse
thank you. i noticed that sio was getting the best quadrant scores too.
nubecoder said:
Just a quick FYI...
The SIO scheduler is supposed to be based on noop and deadline.
I haven't done much testing with it, but it specifically says it's designed for flash devices.
=]
Click to expand...
Click to collapse
Thank you for the amazing rom! one of the best for the epic right now.
kirt231 said:
Thank you for the amazing rom! one of the best for the epic right now.
Click to expand...
Click to collapse
=]
I don't do roms...
Some roms might be using my kernel though, so I understand the confusion.
=]
SIO seems faster but drains the heck out of my battery??
Im using VC deadline and ondemand and Im still at 100% 3 hrs unplugged with some minor messing around....ran the stopwatch for a bit trying to figure out what the hell was buzzing every (as it turns out) 1min. and have been messing around with the ui.
Nothing maujor but a few weeks ago I would have been at 90% by now easy
using smartassv2
with deadline quadrant score 2739
with sio 2733
both are good but as sio is lite version of deadline with a mix of noop so its balanced
deadline can cause some troubles if a program got stuck but its a performer
im using samsung galaxy sl i9003(ti omap3630 at 1.1ghz)
So far I am really loving SIO and smartassV2. My phone is fast when I need it to be and great on battery. From my rough calculations, I drain about 4% an hour when the phone is idle and about 7-10% an hour when I am browsing or watching a video. By the end of an average day, my battery lasts about 14-18 hours.
Ok im looking at kernels and im not going to ask "whats the best?" but im really not understanding the difference.
What im looking for is a kernel thats stable (that seems like all of them), one that allows under-clock/volting (and any other batter saving tricks) and one that will work well with my rom (XenonHD rc3) as most of the kernels seem to be using anyrom i dont think this is an issue.
i have been using the stock kernel then tinys kernel but im wondering if Zen or Air are going to serve me better?
Here is the order im looking at things
Stability
battery
speed
cosmetics
From what i can tell the governors dont seem to matter much as long as there are a few available (performance, interactive, conservative, power-saver) and the schedulers are even less important as they can handle normal use just fine. SIO or no-op or CFQ all work just fine for me. never tried FIFO but it seems kinda restrictive when multitasking
So from a development standpoint could someone explain whats so different in TINY, ZEN, and AIR i would much appreciate your input. They all seem to start from google source, are the compiled different?
Ok so i am trying Zen and i like that the CPU can be clocked lower. but im still not sure about whats best for me. A comparrison chart would be grand but i have no idea what to compare
The major differences between kernels are what kernel version they're compiled from, what modules are compiled into the kernel, which I/O schedulers are included, and which CPU governors are included. Depending on what the kernel dev has included, the kernel tends to run better or worse on specific devices. Unfortunately, it tends to vary quite a bit even within a single device line.
Zen is the best one I've found yet for my device. Others swear by Franco, Air, Trinity, etc. It's really a matter of trial and error on a device-by-device basis.
Finally, your statement about governors and schedulers not being that important is a bit wrong, in my opinion. Schedulers are definitely the lesser of the two, but depending on your usage, you can get a little bit of an I/O performance increase by using the "right" scheduler. The same thing goes for governors. A properly tweaked governor can save a bit of battery and/or boost your performance. Just like the kernels themselves, though, it would vary device-by-device and based on the user's usage type.
Hey everyone!
So I've recently installed Quantum ROM and Quantum Kernel again, and I've noticed some pretty heavy stuttering occasionally (mostly in Minecraft), which I think I've chalked down to an I/O issue.
What's would you all consider the best Governor and I/O settings for a Quantum-based S3 for maximum performance? Battery life doesn't matter, I've got that covered.
I'd go for InteractiveX and SIOPLUS or ROW, personally. I never get lag in ME with those settings, but I do have a different kernel.
epiquiem said:
I'd go for InteractiveX and SIOPLUS or ROW, personally. I never get lag in ME with those settings, but I do have a different kernel.
Click to expand...
Click to collapse
Ahh, okay!
I've settled at the moment for ondemand + zen, which seems to be running pretty well, but I'll take a look into this for sure!
What kernel are you running? I know Quantum doesn't defaultly have SIOPLUS (but it has SIO). Any manual way to install that? Also, does SIOPLUS resolve the apparent issue of having slow random-read speeds on flash devices compared to other schedulers?
I use my own kernel atm (says in my signature ). SIOPLUS is a mix between noop and deadline that improves on the original SIO, so maybe it does fix the slow random-read speeds. One would guess that ROW (read over write) would have the best read speeds, if thats what your looking for. About Quantum not having SIOPLUS, I could build the latest version with SIOPLUS added in and give you the zip, if you want. The kernel description says it has SIOPLUS, actually.
epiquiem said:
I use my own kernel atm (says in my signature ). SIOPLUS is a mix between noop and deadline that improves on the original SIO, so maybe it does fix the slow random-read speeds. One would guess that ROW (read over write) would have the best read speeds, if thats what your looking for. About Quantum not having SIOPLUS, I could build the latest version with SIOPLUS added in and give you the zip, if you want. The kernel description says it has SIOPLUS, actually.
Click to expand...
Click to collapse
SIOPLUS seems to have been removed from the kernel due to an issue forever ago with it crashing people or something. Huh.
I might check out DART soon, as I'm all for flopping between kernels to find what's best! I'd use ROW but it seems pretty...euch, honestly. It's not terrible, but it's not great. Zen seens to be keeping up pretty well in the meanwhile, though.
Thanks for your advice!
Rae Ayanami said:
SIOPLUS seems to have been removed from the kernel due to an issue forever ago with it crashing people or something. Huh.
I might check out DART soon, as I'm all for flopping between kernels to find what's best! I'd use ROW but it seems pretty...euch, honestly. It's not terrible, but it's not great. Zen seens to be keeping up pretty well in the meanwhile, though.
Thanks for your advice!
Click to expand...
Click to collapse
Oof. I wouldn't recommend using Dart until I mark it as stable. It's a work in progress. I would love to have an extra tester around for when I pump out some builds though!
epiquiem said:
Oof. I wouldn't recommend using Dart until I mark it as stable. It's a work in progress. I would love to have an extra tester around for when I pump out some builds though!
Click to expand...
Click to collapse
I'd totally be down for trying it in the future! I'm not sure when I'll have downtime where I can test possibly-unstable things (since I rely on my current S3 for work) but shoot me a PM later on and I can get back to you!
Hi, im on 8.1 and using crdroid's kernel and rom. My battery was tanking until I switched my I/o scheduler to deadline. I'm a n00b with I/o schedulers, so how does deadline work compared to the default scheduler?
Check out this link here to read up on the different Android I/O Schedulers and their differences. Deadline is a solid I/O scheduler on this phone, I used it for a while until I replaced my phone, but I'd be surprised if it made a huge difference on battery life.