- Oct 4, 2012
- 245
- 7
- 81
http://arstechnica.com/gadgets/2016...ew-bland-pricey-but-still-best-android-phone/
" We reached out to the developers of Androbench about this and were told that some shenanigans seem to be happening where the "Direct I/O" calls on the Pixel are actually not that direct. Calls to storage end up going to a RAM cache instead, so you end up with ridiculously high scores of 1GB/s in some cases. Hopefully the storage benchmark developers will be able to get to the bottom of this situation, and we'll update our results when they do."
Despite breaking benchmarks, that sounds like it would add a lot to immediacy of app launches and resumes. Curious to see something like a phonebuff comparison on it, especially with the reigning champ of the iPhone 7 on that speed test.
Now, any OS, or at least consumer facing OS worth its salt should be using idle RAM to keep likely files and applications in it as long as it can. However that cached memory is flagged as purgeable should anything ever need it.
In the Pixels case, it looks like some of the 4GB is a persistent RAM cache which will always be accessed first on a directIO call.
I’d love for this to be investigated more (cough Anandtech cough)
" We reached out to the developers of Androbench about this and were told that some shenanigans seem to be happening where the "Direct I/O" calls on the Pixel are actually not that direct. Calls to storage end up going to a RAM cache instead, so you end up with ridiculously high scores of 1GB/s in some cases. Hopefully the storage benchmark developers will be able to get to the bottom of this situation, and we'll update our results when they do."
Despite breaking benchmarks, that sounds like it would add a lot to immediacy of app launches and resumes. Curious to see something like a phonebuff comparison on it, especially with the reigning champ of the iPhone 7 on that speed test.
Now, any OS, or at least consumer facing OS worth its salt should be using idle RAM to keep likely files and applications in it as long as it can. However that cached memory is flagged as purgeable should anything ever need it.
In the Pixels case, it looks like some of the 4GB is a persistent RAM cache which will always be accessed first on a directIO call.
I’d love for this to be investigated more (cough Anandtech cough)