[Sony Xperia P, U, Sola, Go] jessed54321:
There can be a huge diference!..

I have tested just about all and they are noticeable under different types of workload no doubt using setcpu on my Galaxy S3.

Cfq- "completely fair quing" does just as is sounds.

Bfq- "bandwidth fair quing" similar to cfq but distributes work load fairly giving the exception to prioritize work or task requiring more bandwidth given the app or task has set a priority

, usually asked within a program app.

Row "read over write" gives priority to reading task such as video play back, play intense games and or graphics, overall screen smoothness and cripness , as long as data doesn't require heavy write type of task. Example of an issue I had is, I left I/o in row and had been using ttorent to download a large torrent, uploading was OK but downloading speed was sticking and malfunctioning ttorent up until I switched to cfq. Could not multi task since downloading is obviously a write style task and all priority was to read over write. I love row when I am playing games or want a smooth experience.

Noop- is the idea of first come first serve, get you cake and wait in line to get another peice so if a fat ass is just requiring the whole cake others get hungry but must wait there turn. Bfq can solve that issue especially with sudden heavy multitasking not sticking a task to feel sluggish.

On demand - ramps up processor speed fairly quick returning to idle quick using juice to regain accelerated state once requested again. Conservetive is similar but less quick to jump up and with that said I can get good battery life on performance at times of heavy use do to the stability rather than constant ramps.

---------- Post added at 03:24 AM ---------- Previous post was at 03:19 AM ----------

I have tested just about all and they are noticeable under different types of workload no doubt using setcpu on my Galaxy S3.

Cfq- "completely fair quing" does just as is sounds.

Bfq- "bandwidth fair quing" similar to cfq but distributes work load fairly giving the exception to prioritize work or task requiring more bandwidth given the app or task has set a priority

, usually asked within a program app.

Row "read over write" gives priority to reading task such as video play back, play intense games and or graphics, overall screen smoothness and cripness , as long as data doesn't require heavy write type of task. Example of an issue I had is, I left I/o in row and had been using ttorent to download a large torrent, uploading was OK but downloading speed was sticking and malfunctioning ttorent up until I switched to cfq. Could not multi task since downloading is obviously a write style task and all priority was to read over write. I love row when I am playing games or want a smooth experience.

Noop- is the idea of first come first serve, get you cake and wait in line to get another peice so if a fat ass is just requiring the whole cake others get hungry but must wait there turn. Bfq can solve that issue especially with sudden heavy multitasking not sticking a task to feel sluggish.

On demand - ramps up processor speed fairly quick returning to idle quick using juice to regain accelerated state once requested again. Conservetive is similar but less quick to jump up and with that said I can get good battery life on performance at times of heavy use do to the stability rather than constant ramps.