Quote:
Originally Posted by ziroxs
I used vr/ondemand.
Sent from my GT-I9100 using xda premium
|
Im using CFQ/SmartassV2
Because of this:
6) V(R)
Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.
Advantages:
May be best for benchmarking because at the peak of it's 'form' VR performs best.
Disadvantages:
Performance fluctuation results in below-average performance at times.
Least reliable/most unstable.
3) CFQ
Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.
Advantages:
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
Disadvantages:
Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.
♡ [Device] Samsung Galaxy S2 I9100 ♡
♡ [ROM] ## HCTRom_V7 ## [4.1.2 JB][i9100XXLSE-FOP][OTA] ♡
♡ [KERNEL] Apolo JB Versión ExtremeV0 ♡
♡ [Mod] CrossBreeder 3.15.13.v2 - Descenso drástico de lag - Entropía - DNS ♡
|