5,605,685 Members 48,380 Now Online
XDA Developers Android and Mobile Development Forum

I/O Read Ahead Buffer? Scheduler?

Tip us?
 
ghilliek9
Old
#1  
ghilliek9's Avatar
Senior Member - OP
Thanks Meter 28
Posts: 194
Join Date: Mar 2011
Default I/O Read Ahead Buffer? Scheduler?

I was wondering what others with the Verizon HTC One have set up in their Read Ahead Buffer Size and the Scheduler? I have been reading a lot for the past hour and now I'm just as lost. I am on the NuSense ROM with the OBOne Kernel. I am using Trickster MOD and decided to try 4096 for the Read Ahead Buffer Size and the Deadline Scheduler...no clue if I'm supposed to notice any difference in anything.

Other threads have info using other devices so I was hoping to see what others are using on the One.

Thanks


Horsepower is how fast you hit the wall; torque is how far you take the wall with you.
 
brholt6
Old
#2  
brholt6's Avatar
Senior Member
Thanks Meter 127
Posts: 463
Join Date: Oct 2013
Location: Olathe
Quote:
Originally Posted by ghilliek9 View Post
I was wondering what others with the Verizon HTC One have set up in their Read Ahead Buffer Size and the Scheduler? I have been reading a lot for the past hour and now I'm just as lost. I am on the NuSense ROM with the OBOne Kernel. I am using Trickster MOD and decided to try 4096 for the Read Ahead Buffer Size and the Deadline Scheduler...no clue if I'm supposed to notice any difference in anything.

Other threads have info using other devices so I was hoping to see what others are using on the One.

Thanks
From what I've read, you'll see no benefit going over 1024. I've got mine set at 512.

Sent from my HTC6500LVW using XDA Premium 4 mobile app
Verizon HTC One - S-off'd
iPhone 4 - Retired (thankfully)
Motorola Droid - Retired
The Following User Says Thank You to brholt6 For This Useful Post: [ Click to Expand ]
 
ghilliek9
Old
#3  
ghilliek9's Avatar
Senior Member - OP
Thanks Meter 28
Posts: 194
Join Date: Mar 2011
Quote:
Originally Posted by brholt6 View Post
From what I've read, you'll see no benefit going over 1024. I've got mine set at 512.

Sent from my HTC6500LVW using XDA Premium 4 mobile app
Thanks! I'll scale it down a bit and give that a try.


Horsepower is how fast you hit the wall; torque is how far you take the wall with you.
 
brymaster5000
Old
#4  
brymaster5000's Avatar
Recognized Contributor
Thanks Meter 1117
Posts: 1,519
Join Date: Jan 2012
Location: New Hampshire

 
DONATE TO ME
I've read a bit about it and there is conflicting info out there. I once read that 512 is the sweet spot but another site showed read write performance graphs up to about 4000. The graphs indicated that you would get a gain up to about 3000 (+/-). I typically run mine at 512 with row scheduler. Row was created specifically for mobile phones and works really well for me. My best suggestion is to try them all for a few hours and see what settings work best for your usage. Hope that helps.

Sent from my Ecliptic One.

TEAM ECLIPTIC
Kernel Developer

Like my work? Consider donating to my new phone fund...wouldn't mind deving for the m8.


Devices:
HTC One vzw
Incredible 2 = retired
Nook Color
 
disconnecktie
Old
#5  
disconnecktie's Avatar
Senior Member
Thanks Meter 993
Posts: 4,491
Join Date: Oct 2011
The best way to find out is to test different amounts and see which is best for you. I just ran several benchmarks on all the schedulers and read ahead buffers that are supposed to be the best for mobile devices and they all perform about the same. Each phone will be different. For example, in my testing I found fiops at 1024 did the best consistently.

Sent from my HTC6500LVW using Tapatalk
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes