Well with the release of Imnuts' awesome new kernel I'm finally back to messing around with clocks/volts. I seriously haven't touched Voltage Control since EP1W was released months ago, and even then I only overclocked and undervolted, I never messed with the I/O Schedulers or the CPU Governors. I've decided to use Smartass V2 as the Governor since Imoseyon explained what all the different governors did and that one seems to suit me the best, but as for I/O Schedulers I'm still pretty baffled.
So basically I'm asking if one of you nice XDA users could explain what I/O Schedulers are and what your personal favorite is.
For flash based memory, all IO Schedulers work roughly the same as far as how fast they work. You won't see much of any difference between any of them for 95% of what you do most likely. There is a thread here on XDA in the Nexus One section where someone (or a few people) setup a simple benchmark to test the read/write speed of a few different schedulers and they were all the same, or close enough that it wasn't significant.
blarrick said:
So basically I'm asking if one of you nice XDA users could explain what I/O Schedulers are and what your personal favorite is.
Click to expand...
Click to collapse
To answer the "what they are" question...
They are the rules that the OS uses to determine what order to execute reads and writes to and from block storage (HDD or flash). The primary goal of the majority of them is to find ways to group operations in such a way as to minimize the effect of the seek time on a rotating physical disk, such as an HDD. Different schedulers have different ways of deciding, but, as imnuts said, they'll make very little difference on flash, as flash doesn't have the limitations of a spinning disk, and thus, don't have the problem that I/O schedulers are meant to solve. Certain types of operations or certain individual operations may benefit from one over another in the short term, but over the long run, the total time to complete a larger set of operations on flash should shake out to be roughly the same regardless of the scheduler used.
This thread has a lot of info, scheduler info is in post #3:
http://forum.xda-developers.com/showthread.php?t=1369817
Related
Ok so i read this post but I don't understand any of it. Can someone explain it to me simple. All I know is noop the one I'm using now seems to not max out to 1512 as much as the other ones so maybe it will be better one battery life.
http://forum.xda-developers.com/showthread.php?t=1558153
Sent from my HTC Sensation 4G using xda premium
iverson3-1 said:
Ok so i read this post but I don't understand any of it. Can someone explain it to me simple. All I know is noop the one I'm using now seems to not max out to 1512 as much as the other ones so maybe it will be better one battery life.
http://forum.xda-developers.com/showthread.php?t=1558153
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Hey,
To the best of my understanding, they are I/O schedulers based on certain algorithms.
It's easy to explain if you know how queues are implemented.
noop is just a First In First Out standard queue of I/O operations.
cfq (Completely Fair Scheduling) is similar to the Round Robin algorithm and basically allots a fixed execution time for each I/O operation (they are implemented as a circular queue)
deadline is like a priority queue with an aging concept. Basically it adds a dealine for each I/O operation & implements a priority queue
Furthermore, there are 2 queues, one for read & one for write operations.
I'm sorry if this doesn't make sense, you just asked a technical question & I don't know how to explain better than this!
EDIT: Okay, I didn't see the link, most of the info I gave is present there.
EDIT: Here's an analogy, if people were queuing up to buy ice cream:
noop would implement the first come first serve rule.
cfq would let each person to buy one ice cream at a time & go back to the end of the queue if he wants another.
deadline would keep a separate queue for certain people (like older people & people who have been waiting for too long; somewhat setting a priority) & would serve the separate queue first.
Tried my best.
kgs1992 said:
Hey,
To the best of my understanding, they are I/O schedulers based on certain algorithms.
It's easy to explain if you know how queues are implemented.
noop is just a First In First Out standard queue of I/O operations.
cfq (Completely Fair Scheduling) is similar to the Round Robin algorithm and basically allots a fixed execution time for each I/O operation (they are implemented as a circular queue)
deadline is like a priority queue with an aging concept. Basically it adds a dealine for each I/O operation & implements a priority queue
Furthermore, there are 2 queues, one for read & one for write operations.
I'm sorry if this doesn't make sense, you just asked a technical question & I don't know how to explain better than this!
EDIT: Okay, I didn't see the link, most of the info I gave is present there.
EDIT: Here's an analogy, if people were queuing up to buy ice cream:
noop would implement the first come first serve rule.
cfq would let each person to buy one ice cream at a time & go back to the end of the queue if he wants another.
deadline would keep a separate queue for certain people (like older people & people who have been waiting for too long) & would serve the separate queue first.
Tried my best.
Click to expand...
Click to collapse
Thanks. Nice analogy. I understand a lil better now.
Sent from my HTC Sensation 4G using xda premium
which would be best for general use of our dual core sensation?
i was told that dualcore doesnt work that well with all schedulers
What is better
What is best to use for performance , Cfq , noop Or deadline?
Envious_Data said:
What is best to use for performance , Cfq , noop Or deadline?
Click to expand...
Click to collapse
i am using cfq and i can say that performance is very good
I don't have that many apps running, so cfq seems to work best for me.
i use xondemand most of the time, sometimes ondemand or intellidemand depending on kernel. those cpu govs works best with sio scheduler, imo.
i have no idea which is the best applicable to htc sensation even after the brilliant explanation by the TS.
i guess i can never tell which is the best. I was using cfq all along which brick kernel (because it was set as default)
After flashing a newer version of ViperS 1.4.0, the default became nooq for some reasons i do not know, i guess i will just give it a try.
egg_n_ham said:
i have no idea which is the best applicable to htc sensation even after the brilliant explanation by the TS.
i guess i can never tell which is the best. I was using cfq all along which brick kernel (because it was set as default)
After flashing a newer version of ViperS 1.4.0, the default became nooq for some reasons i do not know, i guess i will just give it a try.
Click to expand...
Click to collapse
you can change it by using setcpu or system tuner or
it can be done in system>etc>init.qcom.post_boot.sh by editing with any file manager(maybe i am wrong with this one)
I have tried many scheduler and governor settings but i always endup with DEADLINE as I/O scheduler and ONDEMAND as CPU governor!
Just give it a try! :good:
kgs1992 said:
Hey,
To the best of my understanding, they are I/O schedulers based on certain algorithms.
It's easy to explain if you know how queues are implemented.
noop is just a First In First Out standard queue of I/O operations.
cfq (Completely Fair Scheduling) is similar to the Round Robin algorithm and basically allots a fixed execution time for each I/O operation (they are implemented as a circular queue)
deadline is like a priority queue with an aging concept. Basically it adds a dealine for each I/O operation & implements a priority queue
Furthermore, there are 2 queues, one for read & one for write operations.
I'm sorry if this doesn't make sense, you just asked a technical question & I don't know how to explain better than this!
EDIT: Okay, I didn't see the link, most of the info I gave is present there.
EDIT: Here's an analogy, if people were queuing up to buy ice cream:
noop would implement the first come first serve rule.
cfq would let each person to buy one ice cream at a time & go back to the end of the queue if he wants another.
deadline would keep a separate queue for certain people (like older people & people who have been waiting for too long; somewhat setting a priority) & would serve the separate queue first.
Tried my best.
Click to expand...
Click to collapse
Explain a new scheduler that is row which is available now in set cpu. And if u could explain governor also plz go ahead . i would be very thankful!
kgs1992 said:
Hey,
To the best of my understanding, they are I/O schedulers based on certain algorithms.
It's easy to explain if you know how queues are implemented.
noop is just a First In First Out standard queue of I/O operations.
cfq (Completely Fair Scheduling) is similar to the Round Robin algorithm and basically allots a fixed execution time for each I/O operation (they are implemented as a circular queue)
deadline is like a priority queue with an aging concept. Basically it adds a dealine for each I/O operation & implements a priority queue
Furthermore, there are 2 queues, one for read & one for write operations.
I'm sorry if this doesn't make sense, you just asked a technical question & I don't know how to explain better than this!
EDIT: Okay, I didn't see the link, most of the info I gave is present there.
EDIT: Here's an analogy, if people were queuing up to buy ice cream:
noop would implement the first come first serve rule.
cfq would let each person to buy one ice cream at a time & go back to the end of the queue if he wants another.
deadline would keep a separate queue for certain people (like older people & people who have been waiting for too long; somewhat setting a priority) & would serve the separate queue first.
Tried my best.
Click to expand...
Click to collapse
Great way explain .. Terrific
Is it bfq or cfq?
And should I choose performance over conservative in voltage control?
I always got kernel panic when I undervolted, too.
Sent from my Saurom'd Infuse
I always left my infuse CPU/voltage at stock settings....never had any probs and the phone was fast enough and lasted me the day...not that is helpful for you question...but if I were you I wouldnt mess with CPU and voltage...but that's just me
Sent from my HTC PH39100 using Tapatalk 2
Crinkypops said:
Is it bfq or cfq?
And should I choose performance over conservative in voltage control?
I always got kernel panic when I undervolted, too.
Sent from my Saurom'd Infuse
Click to expand...
Click to collapse
I have been using cfq with ondemand, and undervolt 50 mV each not much but its stable. Performance setting will kill your battery.
I was under the impression that noop is theoretically the best I/O scheduler for flash devices, but I can't find any good benchmarks comparing its performance to the others in a typical real world smartphone workload.
Btw I don't consider using "time dd" to be very helpful in replicating a real world multitasking workload. What's the point of testing a scheduler with a single file read or write? You may or may not have background processes reading or writing at the time of the test, but you wouldn't necessarily know it. As such, I would take any single threaded I/O benchmarks or simple tests with a grain of salt, even on a smartphone.
If someone with more knowledge of smartphone I/O access patterns sees a need to correct me on this, I would appreciate it. I'm an experienced *nix admin, but pretty much still a noob regarding android.
Sent from my SGH-I997 using xda app-developers app
I've searched the forums for a while now and read up on these topics. However, I cannot seem to come to a conclusion about what settings to apply.
I've messed about with them. When I selected Conservative as my governor and SIO as my Scheduler, any additional CPU work (playing a game) would cause my music player application to stop. So I'm guessing it was holding the CPU back a bit.
My current settings goes as follows:
Awake:
CPU Max: 1024000
CPU Min : 245760
Governor : SmartassV2
Asleep: Same as awake(asking for trouble?)
I/O : SIO( I have read in a post that this was one of the better ones)
ROM : Fallout V5.0
Kernel : Fallout 3.0.42
All changes were done using Fallout Tweaks
Now, my main question...
For day to day stable use, what settings would you recommend ? I don't mind over clocking to 1.2Mhz(That should be safe, right?) but I don't understand which Governor, Scheduler and frequencies to use. I understand that there is a specific way in which you pair Awake and Asleep Governors and that some combinations are bad but I have no clue what this is. I'm looking for something that will keep regular phone use smooth and avoid lag but battery consumption is important. I know that this is asking for the best of both worlds, but take into account that I'm not asking for any heavy duty processing... Just smooth scrolling, messaging, browsing, music playing etc. without them forcing the other not to work (As stated in the problem above)
Well, now that thats over I would also like to suggest someone write a post involving these issues, if possible. In my searches, I have found information detailing the Schedulers and Governors(For other phones) but these just explain how they work and not definitively explaining which is better for a specific use and how they should be paired in an awake+asleep state. One specifically for us Desire S owners would be nice.
As such, it would also be nice to understand what is the difference between these awake/asleep states and why a certain scheduler should be used in each.
I don't mean to sound demanding or rude but perhaps some of the gurus on here have the time and would like to help noobs like myself or guide me to the correct post. Thank you !
DieLyn said:
I've searched the forums for a while now and read up on these topics. However, I cannot seem to come to a conclusion about what settings to apply.
I've messed about with them. When I selected Conservative as my governor and SIO as my Scheduler, any additional CPU work (playing a game) would cause my music player application to stop. So I'm guessing it was holding the CPU back a bit.
My current settings goes as follows:
Awake:
CPU Max: 1024000
CPU Min : 245760
Governor : SmartassV2
Asleep: Same as awake(asking for trouble?)
I/O : SIO( I have read in a post that this was one of the better ones)
ROM : Fallout V5.0
Kernel : Fallout 3.0.42
All changes were done using Fallout Tweaks
Now, my main question...
For day to day stable use, what settings would you recommend ? I don't mind over clocking to 1.2Mhz(That should be safe, right?) but I don't understand which Governor, Scheduler and frequencies to use. I understand that there is a specific way in which you pair Awake and Asleep Governors and that some combinations are bad but I have no clue what this is. I'm looking for something that will keep regular phone use smooth and avoid lag but battery consumption is important. I know that this is asking for the best of both worlds, but take into account that I'm not asking for any heavy duty processing... Just smooth scrolling, messaging, browsing, music playing etc. without them forcing the other not to work (As stated in the problem above)
Well, now that thats over I would also like to suggest someone write a post involving these issues, if possible. In my searches, I have found information detailing the Schedulers and Governors(For other phones) but these just explain how they work and not definitively explaining which is better for a specific use and how they should be paired in an awake+asleep state. One specifically for us Desire S owners would be nice.
As such, it would also be nice to understand what is the difference between these awake/asleep states and why a certain scheduler should be used in each.
I don't mean to sound demanding or rude but perhaps some of the gurus on here have the time and would like to help noobs like myself or guide me to the correct post. Thank you !
Click to expand...
Click to collapse
I use new amida's kernel with this settings:
Awake:
CPU Max: 1497 Mhz
CPU Min : 768 Mhz
Governor : Brazilianwax or reaper if you use the fallout kernel
Asleep:
CPU Max: 768 Mhz
CPU Min : 245 Mhz
Governor : SmartassV2
With this you can get a great performance for gaming and save battery during sleep
Sorry for my bad English
DieLyn said:
I've searched the forums for a while now and read up on these topics. However, I cannot seem to come to a conclusion about what settings to apply.
I've messed about with them. When I selected Conservative as my governor and SIO as my Scheduler, any additional CPU work (playing a game) would cause my music player application to stop. So I'm guessing it was holding the CPU back a bit.
My current settings goes as follows:
Awake:
CPU Max: 1024000
CPU Min : 245760
Governor : SmartassV2
Asleep: Same as awake(asking for trouble?)
I/O : SIO( I have read in a post that this was one of the better ones)
ROM : Fallout V5.0
Kernel : Fallout 3.0.42
All changes were done using Fallout Tweaks
Now, my main question...
For day to day stable use, what settings would you recommend ? I don't mind over clocking to 1.2Mhz(That should be safe, right?) but I don't understand which Governor, Scheduler and frequencies to use. I understand that there is a specific way in which you pair Awake and Asleep Governors and that some combinations are bad but I have no clue what this is. I'm looking for something that will keep regular phone use smooth and avoid lag but battery consumption is important. I know that this is asking for the best of both worlds, but take into account that I'm not asking for any heavy duty processing... Just smooth scrolling, messaging, browsing, music playing etc. without them forcing the other not to work (As stated in the problem above)
Well, now that thats over I would also like to suggest someone write a post involving these issues, if possible. In my searches, I have found information detailing the Schedulers and Governors(For other phones) but these just explain how they work and not definitively explaining which is better for a specific use and how they should be paired in an awake+asleep state. One specifically for us Desire S owners would be nice.
As such, it would also be nice to understand what is the difference between these awake/asleep states and why a certain scheduler should be used in each.
I don't mean to sound demanding or rude but perhaps some of the gurus on here have the time and would like to help noobs like myself or guide me to the correct post. Thank you !
Click to expand...
Click to collapse
u might want to read above this http://forum.xda-developers.com/showthread.php?p=19846297
nazri5363 said:
u might want to read above this http://forum.xda-developers.com/showthread.php?p=19846297
Click to expand...
Click to collapse
Ah, thank you. I did read that and it was the one I was referring to in my post. "Other phones" as it is for the SGS II.
DieLyn said:
Ah, thank you. I did read that and it was the one I was referring to in my post. "Other phones" as it is for the SGS II.
Click to expand...
Click to collapse
i am on fallout also...currently i am using intellidemant min/ max 245-1024 awake and 245-768 smartassv2 in asleep....basically the governor are the same i guess no matter from which device....my current setting quite good with no lag...btw i am using noop i/o scheduler...
DieLyn said:
Ah, thank you. I did read that and it was the one I was referring to in my post. "Other phones" as it is for the SGS II.
Click to expand...
Click to collapse
That is relative, you need one governor or other depend if you want performance, battery duration or a balanced combination...try one and another to get your best combination of them :fingers-crossed:
jos3ang3l said:
That is relative, you need one governor or other depend if you want performance, battery duration or a balanced combination...try one and another to get your best combination of them :fingers-crossed:
Click to expand...
Click to collapse
agreed....perhaps u should try to flash amidabuddha latest kernel...3.0.43 is the latest kernel....
nazri5363 said:
agreed....perhaps u should try to flash amidabuddha latest kernel...3.0.43 is the latest kernel....
Click to expand...
Click to collapse
Of course, I flashed it too
Sent from my HTC Desire S using xda premium
Please forgive me for asking, if this has already been answered. Question for the Devs... Will any future releases (kernel only, or ROM) include a wider selection of governors and i/o schedulers, or is this device limited to the ones already available for some reason?
Coming over from HTC Glacier and Doubleshot, there were more choices than I knew what to do with. This is my first Samsung device.
Not that I'm complaining, I've found a combination that works good for me. I just wanted to know.
By the way - you guys are doing some great work over here. I'm loving this phone. Thanks!
This would be done on the kernel level and it is certainly possible to add more options but doing so can make things less stable.
If there is something you think may work better you could ask a dev if implementing has been tried and what the result is otherwise the main kernel source is available on github and there are many guides to build yourself and test
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
This would be done on the kernel level and it is certainly possible to add more options but doing so can make things less stable.
If there is something you think may work better you could ask a dev if implementing has been tried and what the result is otherwise the main kernel source is available on github and there are many guides to build yourself and test
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm sure the devs have sound reasoning behind their choices. I was just curious to find out if it was something device specific, as opposed to dev preference. I don't know that I would go so far, as to tamper with the kernel source myself. I don't have those skills yet. I may look into that in the future. I'm always willing to learn.
jadrt09 said:
Please forgive me for asking, if this has already been answered. Question for the Devs... Will any future releases (kernel only, or ROM) include a wider selection of governors and i/o schedulers, or is this device limited to the ones already available for some reason?
Coming over from HTC Glacier and Doubleshot, there were more choices than I knew what to do with. This is my first Samsung device.
Not that I'm complaining, I've found a combination that works good for me. I just wanted to know.
By the way - you guys are doing some great work over here. I'm loving this phone. Thanks!
Click to expand...
Click to collapse
Hit the app store and grab CPU Tuner, you might find it's got what you need.
yohan4ws said:
Hit the app store and grab CPU Tuner, you might find it's got what you need.
Click to expand...
Click to collapse
Thanks, I'll check that one out but I believe that apps like that will only allow you to select from the governors and schedulers that are available in the kernel itself - not implement one that isn't there. I'd like to try out intellidemand, or smartassV2 with this device.
Right now, I'm using the interactive governor & sio. Then using SetCPU with profiles for screen-off, screen-on, and charging. This is kind of giving me the results I wanted. Sort of gives me an interactiveX, I guess? SetCPU doesn't show me both cores, so I really don't know. Also have tried Kernel Tuner and Trickster with mixed results.
jadrt09 said:
Thanks, I'll check that one out but I believe that apps like that will only allow you to select from the governors and schedulers that are available in the kernel itself - not implement one that isn't there. I'd like to try out intellidemand, or smartassV2 with this device.
Right now, I'm using the interactive governor & sio. Then using SetCPU with profiles for screen-off, screen-on, and charging. This is kind of giving me the results I wanted. Sort of gives me an interactiveX, I guess? SetCPU doesn't show me both cores, so I really don't know. Also have tried Kernel Tuner and Trickster with mixed results.
Click to expand...
Click to collapse
Just downloaded CPU Tuner. This appears to be a better alternative to the other ones I've tried. I can get what I want without trying to mess with the kernel. Gonna run the "Sophisticated" config + Performance profile for a while and see how it goes. Thanks! :good:
jadrt09 said:
Please forgive me for asking, if this has already been answered. Question for the Devs... Will any future releases (kernel only, or ROM) include a wider selection of governors and i/o schedulers, or is this device limited to the ones already available for some reason?
Coming over from HTC Glacier and Doubleshot, there were more choices than I knew what to do with. This is my first Samsung device.
Not that I'm complaining, I've found a combination that works good for me. I just wanted to know.
By the way - you guys are doing some great work over here. I'm loving this phone. Thanks!
Click to expand...
Click to collapse
my roms have more freedom of the kernel with this...current governors in my builds are: conservative, ondemand, userspace, powersave, interactive, and performance. Current I/O schedulers are noop, deadline, row, cfq, and sio. i will be exapanding on this soon but sio and interactive or sio and ondemand have given the bast stability for me.
REV3NT3CH said:
my roms have more freedom of the kernel with this...current governors in my builds are: conservative, ondemand, userspace, powersave, interactive, and performance. Current I/O schedulers are noop, deadline, row, cfq, and sio. i will be exapanding on this soon but sio and interactive or sio and ondemand have given the bast stability for me.
Click to expand...
Click to collapse
I've been running your Carbon ROM for a little while and I've been pretty pleased with it. I've settled on the interactive and sio combination but I wanted to have a little more control. Most of the time I just text and do a little web browsing, so I want to extend battery life. But I have access to a lot of wi-fi hotspots, so then I can plug in for some gaming or Netflix. It's nice to have the performance amped up then. I seemed to have good results with intellidemand and smartass variations on my other phones.
I appreciate your work, thanks!
jadrt09 said:
I've been running your Carbon ROM for a little while and I've been pretty pleased with it. I've settled on the interactive and sio combination but I wanted to have a little more control. Most of the time I just text and do a little web browsing, so I want to extend battery life. But I have access to a lot of wi-fi hotspots, so then I can plug in for some gaming or Netflix. It's nice to have the performance amped up then. I seemed to have good results with intellidemand and smartass variations on my other phones.
I appreciate your work, thanks!
Click to expand...
Click to collapse
your very welcome...as ive stated before i will be adding some more here soon. i have a couple of new rom builds im working on and an update to another...i definitely need to work on the kernel as ive done little patches here and there but nothing too big....think within the next few weeks ill do a big update to it and update all my roms with it
Perhaps you could release a flashable kernel for people on cm?
Sent from my SGH-T699 using Tapatalk
REV3NT3CH said:
my roms have more freedom of the kernel with this...current governors in my builds are: conservative, ondemand, userspace, powersave, interactive, and performance. Current I/O schedulers are noop, deadline, row, cfq, and sio. i will be exapanding on this soon but sio and interactive or sio and ondemand have given the bast stability for me.
Click to expand...
Click to collapse
Errr What advantages are there from sio over the other i/o schedulers. That's the only addition between your list and what we are currently enabling.
Magamo said:
Errr What advantages are there from sio over the other i/o schedulers. That's the only addition between your list and what we are currently enabling.
Click to expand...
Click to collapse
Simple I/O (sio) scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.
REV3NT3CH said:
Simple I/O (sio) scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.
Click to expand...
Click to collapse
I notice a difference in performance when I change governors but I can't say that I notice a difference at all, when changing i/o schedulers. My understanding is that certain combinations are supposed to work better together. I just remember that devs of certain mods I've used had a preference for sio o over the others. Not sure why, but it worked, so I've stuck with it...
Hi and forgive my 'noobness' but do you guys think there's a significal difference in performance/battery if I use a different scheduler, because I googled a lot about the differences between all of them and I actually understand what all they do and their main advantages. Some people say that ROW feels quicker than deadline but Im not sure if its placebo. A guy in andrux-and-me(dot)blogspot(dot)com(dot)es/2014/05/io-schedulers-and-performance-2(dot)html compared/tested them so that's why I was wondering.
I always use the default scheduler in ElementalX (ROW I think) and never had any troubles but I also believe that Franco uses deadline so I was wondering what the experts here have to say.
Difference isn't too noticeable for most.
DamnItLukasz said:
Hi and forgive my 'noobness' but do you guys think there's a significal difference in performance/battery if I use a different scheduler, because I googled a lot about the differences between all of them and I actually understand what all they do and their main advantages. Some people say that ROW feels quicker than deadline but Im not sure if its placebo. A guy in andrux-and-me(dot)blogspot(dot)com(dot)es/2014/05/io-schedulers-and-performance-2(dot)html compared/tested them so that's why I was wondering.
I always use the default scheduler in ElementalX (ROW I think) and never had any troubles but I also believe that Franco uses deadline so I was wondering what the experts here have to say.
Click to expand...
Click to collapse
I've done benchmarks with some schedulers at different buffer sizes, and other users have done way more extensive testing.
it is heavily device dependent and benchmarking does not exactly reflect real-life usage.
your best bet is to find one that works for you.
my two most common are row and fiops at 512 or 1024 buffer.
it all depends how personally you use your device. how you use it would show you which one to use. i use only deadline. it works perfectly for how i use my device.