We expect the Google Pixel9Pro XL to deliver impressive AI capabilities when it arrives later this year. This is because the recently discovered Geekbench CPU benchmark results (via MySmartPrice and AndroidCentral) show what changes Google can make to enhance the entire Pixel9 series.

Looking at the main results at the top of the list, we can see that the Pixel9Pro XL outperforms what pixel8Pro got during its own testing. You can see that. According to CPU information, the chip in the Pixel9Pro XL (assumed to be named Tensor G4) has one less CPU core than the TENSOR G3 in the PIXEL8Pro, but to compensate for that,

More interestingly, the device is running on the 12GB to 16GB RAM offered by the Pixel8Pro and previous Pro Pixels. You can see that it is. The Samsung Galaxy S24Ultra offers 12GB of RAM, while the iPhone15Pro is only 8GB, so that's a fair amount of RAM that Google uses. This will give the new Pixel the top-spec model of OnePlus12 and some game-focused phone companies like ROG Phone8Pro, which offers 16GB or 24GB of RAM, which is likely to be good news for games at Pixel9Pro, but the extra RAM is likely to help with AI capabilities, and will be a big part of the Pixel family of the PIXEL8 series. It became the focus. With Samsung's Galaxy AI and Apple Intelligence now offering competition, Google may be looking for ways to get the edge, including new features and hardware improvements.

It is believed that the Pixel9 series will expand to 3 models this year, rather than 2 as in the past 3 years. Pixel9Pro XL will be the same size as Pixel8Pro 6.7 inches, while Google Pixel9Pro will be converted to the new 6.1 inch phone size. The basic Google Pixel9 should be 6.0 inches, which is a bit smaller than the previous basic Pixel models.

Google typically launches its flagship Pixel phones every year in the 10th month, so the new phones are months away from their expected debut, so final performance can be seen here however, despite how well they fit into other rumors, as they could also trick the Geekbench browser to misidentify the device. Please note that this may not be the case.