iPhone 7 humiliates the Galaxy Note 7 in a performance test published just a few hours ago, and if you look at it you will also understand why the word humiliates worth using. Very important to say from the beginning is that we are talking about the iPhone 7 and not the iPhone 7 Plus, so only 2 GB of RAM are available for this device, but they are enough.
The test is done by comparing the opening period of native and third-party applications, plus a small processing test, that is, a timelapse is created from a video clip using Adobe Photoshop. In all these tests, the iPhone 7 shines with its A10 Fusion chip and quad-core processor, the Samsung Galaxy Note 7 being far, far behind.
In the first part of the test, the Galaxy Note 7 manages to be slightly faster than the iPhone 7, until the moment the games are opened, where the first gap between them appears. The distance becomes even greater when that timelapse is created using the Adobe Photoshop application, and when the applications in the background are reopened, things are worse.
iPhone 7 humiliates Galaxy Note 7 in a performance test
iPhone 7 finished the first part of the tests in one minute and 14 seconds, with no less than 50 seconds before the Samsung Galaxy Note 7, the difference being enormous from the start. When it came time for the applications to be reopened from the background, the iPhone 7 needed only 26 seconds, its total time being 1 minute and 40 seconds.
The Samsung Galaxy Note 7 didn't fare as well, needing the 3 minutes and 14 seconds to complete the test, so with 1 minute and 34 seconds more than the iPhone 7. Basically, the Galaxy Note 7 needed almost 2 times more time than the iPhone 7 to complete the entire test, something that has not happened so far in any other comparison.
Unfortunately, the Galaxy Note 7 showed its weaknesses in this comparative test, and that RAM memory disappears quickly the more complex things you do on the terminal. In this idea, when reopening other closed applications, they will not be accessed from RAM, but will reload all the data, and this was practically, again, the big problem of the terminal.
