The Google Pixel 3 Review: The Ultimate Camera Testby Andrei Frumusanu on November 2, 2018 11:00 AM EST
- Posted in
- Snapdragon 845
- Pixel 3
Pixel phones have been known to be among the best performing Android devices in the market. This is mainly due to the Pixel’s performance team taking the time and attention to tweak the software stack – kernel and userspace alike. This is one of the benefits of being one of the last flagships out of the gate for a given generation, as it gives time to optimize the performance. The Pixel 3 comes with the Snapdragon 845, and I’ve written many times this year how Qualcomm’s software, and in particular the kernel scheduler was a very significant factor as to why this year’s Snapdragon phones performed so marvellously.
One of the big questions I posed myself early in the year is exactly how Google planned to handle Qualcomm’s great divergence from upstream, and the divergence from the Google common kernel. As a reminder, the Google common kernel is now the “official” branch on which SoC vendors should be basing their BSP (board support packages, essentially the software stack) for their own products. This is a collaborative effort between vendors (Mainly Google, Qualcomm and Arm), and it’s also the target where Arm pushes its own EAS patches.
The matter of fact is, for the Pixel 3, Google is simply using Qualcomm’s custom scheduler. This is both a great win for Qualcomm given the expected device performance of the Pixel 3, and quite a blow to Arm’s own efforts, as the EAS improvements over the last year are just simply not being used. Qualcomm’s efforts as well as the resulting product are just too good to pass on, and I’m very much expecting next year to finally be a watershed moment where other vendors finally abandon attempts to keep things minimalistic, and in line with upstream Linux, and finally see the immense value in investing in actual immediate benefits for consumer devices of a given generation.
Starting with PCMark’s Web Browsing 2.0 test, the Pixel 3 leads the pack, with a slight advantage over other Snapdragon 845 phones. The reason here is that Google seemingly uses the most up-to-date scheduler, as well as has some possible file I/O advantages which I’ll get into a bit later. There are also possible OS side improvements in the libraries, as the Pixel 3’s ship with Android 9.
I’ve updated the performance results for past Pixels with the newest OS updates, as well as for devices like the OnePlus 6 as these have received their OS updates as well.
In the writing test, which is probably PCMark’s most important as well as representative benchmark, the Pixel 3 saw a big leap in performance over the previous Pixels – however I think this was due to Android 9 itself, as we also saw a big jump in the OnePlus 6’s performance with the latest OS update.
The photo editing test is very much a scheduler responsivity test as modern devices are able to complete the workloads relatively fast at their peak performance states. Here the score wildly fluctuates depending on how fast the DVFS mechanism is, and we see the Pixel 3 among the best performers.
The data manipulation score is extremely high on the Pixel 3 compares to other phones, including the OnePlus 6. I wasn’t able to verify this empirically, but glancing over the scheduler the Pixel has some unique updates to it which facilitate better responsiveness and scheduling of single big tasks, and the data manipulation test is such a workload with a big single-threaded component.
Overall, the Pixel 3 takes the top position in PCMark, all thanks to its scheduler improvements as well as a slight advantage due to it running Android 9.
Moving onto web browser tests, the Pixel 3 largely matches the other Snapdragon 845 devices. This is no surprise as Speedometer 2.0 is a high constant throughput ST benchmark, and as such isn’t as affected by scheduler as PCMark.
Apple still has a considerable performance lead here. After our recent iPhone XS review and SoC deep-dive, I’m more leaning towards the explanation that a big part of the advantage here is purely due to hardware and the microarchitectural advantages of Apple’s CPUs, with part of it also being Apple’s Nitro JS engine.
WebXPRT also looks in line with other Snapdragon 845 devices.
Pixel 3 – Now using F2FS
Section with credit and input by Park Ju Hyung (@arter97)
The Pixel 3 now has switched over from an EXT4 filesystem, to the F2FS filesystem. Google explains this switch due to the fact that F2FS now supports inline block encryption which has been the last major roadblock as to why Google hadn’t made the switch earlier.
Inline block encryption uses the SoC’s inline cryptographic engines, which just serve as an intermediate hardware layer to the NAND and offload any encryption workloads that were initially in past devices performed by the CPU.
The switch to F2FS now gives the Pixel 3 a number of advantages over previous filesystem; Previously, SQLite (which is used by almost all database files under Android) used another 'journaling' on its own to prevent corruption. This caused “double journaling” on top of EXT4, which in itself is a journaling filesystem. Since F2FS doesn’t need this kind of protection and the Pixel 3 includes Google’s SQLite changes in Android 8.1, the Pixel 3 is able to take advantage of this, as well as any other F2FS based device from other vendors which have the corresponding OS patches.
The result is that this will enable much higher write/commit speeds for SQLite, not to mention less wear and tear to the underlying UFS storage. Also, the Pixel 3 turned off barriers for fsync() system calls, which will improve general random I/O write speeds by a significant margin.
Another big improvement for file I/O is the implementation of “Host Performance Booster” in the kernel and UFS controller firmware stack. HPB is essentially caching of the NAND chip’s FTL (flash translation layer) L2P (logical to physical) mapping tables into the hosts (SoCs) main memory. This allows the host driver to look up the target L2P entry directly without betting on UFS’s limited SRAM to have a cache-hit, reducing latency and greatly increasing random read performance. The authors of the feature showcase an improvement of 59-67% in random I/O read performance due to the new feature. It’s worth to mention that traditional Android I/O benchmarks won’t be able to show this as as those tend to test read speeds with the files they’ve just created.
Overall, the Pixel 3 is the fastest Android device on the market right now. The one thing that puts it above other devices such as the OnePlus 6 is a noticeable faster response-time when opening applications – either a framework related boost or just an effect of the faster file I/O.
Post Your CommentPlease log in or sign up to comment.
View All Comments
jospoortvliet - Saturday, November 3, 2018 - linkIt combines multiple images into one - not something you would manually be able to reasonably do. I mean, maybe, but it is very hard. It isn't just applying some filters you can do on any picture.
Impulses - Saturday, November 3, 2018 - linkUm, HDR is a pretty common technique for photographers and the burst rates and high end stabilization of today's cameras make it more accessible than ever... So using HDR or HDR-like methods (Google actually combines multiple frames with similar exposures IIRC) to increase DR or average noise out is not the least bit uncommon, it's not hard to do and a lot of software packages automate it to a very high degree.
Where Google's approach differs significantly and what makes it so accessible as the primary mode (and part of what makes Night Sight great, it's just building upon the same algorithms but with slower shutter speeds) is in the smart tiling they employ before stacking all the frames. That's what makes it usable even with subject motion in the frame and other variable lighting conditions... They break each frame down into tiles and they combine those tiles individually, dropping some as needed if the subject moved across tiles or blurred out... That's obviously way beyond the normal post processing techniques people do by hand.
Impulses - Saturday, November 3, 2018 - linkNote: I'm referring mostly to stills in standard HDR+ and Night Sight, what they've done with Super Res Zoom is somewhat impressive but still pretty gimmicky in the end IMO... If I needed a longer focal length I'd just shoot a discrete camera or a phone with a longer focal length in optics.
Ikefu - Friday, November 2, 2018 - linkKeep us posted on when the LG V40 comparison is coming! I'm between a 3 XL and a V40 and these reviews are phenomenal. Love it Andrei!
Andrei Frumusanu - Friday, November 2, 2018 - linkIf the V40 is anywhere near the G7's camera performance, which some reviews have hinted at, then the 3XL might be a better choice.
Ikefu - Friday, November 2, 2018 - linkTrue, but I'm slightly addicted to the wide angle camera for landscapes and stadiums. I'm still holding on to my shred of hope when your review hits.
Andrei Frumusanu - Friday, November 2, 2018 - linkI'll do a quick check on the V40 tomorrow and write back here - the Mate 20's review is next in line to be published first.
Arbie - Friday, November 2, 2018 - linkGreat, because the V30 and V40, along with the Samsung S9 and S9+, seem to be the only brand phones supporting all the T-Mobile bands (eg. 71). That really limits choice if you want max compatibility with that carrier.
Which leads me to wonder how the S9 compares in general to the S9+; primarily in low light. The latter is well-documented here.
Phenomenal review overall, thanks.
imaheadcase - Friday, November 2, 2018 - linkThe stand is not bundled with the phone, its a separate purchase. Not sure why you said that.
Andrei Frumusanu - Friday, November 2, 2018 - linkI wrote that it was bundled with the review phone, I edited the sentence to clarify this.