System might still be be indexing (or whatever the iOS equivalent is). Try a hard reset and re-run?
Also was that previous score benched on your phone or was it a different device?
Perhaps that benchmark app needs to be updated due to conflicts with APFS and the way it reads to the app itself?
I tested it at various times, before and after reset, before and after reindexing.
The previous score was the reference benchmark in the app but I had tested it and I got a similar number (just didn't save the result since it was almost identical).
[doublepost=1490801319][/doublepost]
Possibly - then there's the slower 3D scores to think about too (look at the bottom of the pic)
To be honest I think it's a bit foolish to expect accurate results from a benchmarking app after an iOS .X update, let alone an entirely new filesystem before the app itself receives any updates.Possibly - then there's the slower 3D scores to think about too (look at the bottom of the pic)
To be honest I think it's a bit foolish to expect accurate results from a benchmarking app after an iOS .X update, let alone an entirely new filesystem before the app itself receives any updates.
As the poster above asked, have you seen any performance degradation or are we looking at numbers for numbers sake? If it's the latter, wait for the app to be updated before taking the results seriously.
I sincerely doubt that APFS has caused I/O speed to actually drop, in fact from the WWDC demos (admittedly on a mac, but I can't imagine such a drastic deviation to iOS) performs many function at a breathtakingly faster speed.Real world usage seems fluid - no issues I can see, but then again the SE has an excess of speed so maybe I'm just not hitting the bottleneck.
So it could be that
Now, I do storage for a living, and if the Antutu benchmark follows the API rules, it should NOT have to be rewritten. If anything, the results show that doing the exact same system calls, in a 64-bit app, that's current as of 10.2.1, the new OS is half the speed for I/O.
- There IS a degradation, and I simply don't feel the degradation since I don't do something that stresses the IO apart from the benchmark (I have the 64GB SE, even at the reduced speed it's faster in IO than many other models) OR
- The benchmark needs to be updated as many of you said
D
I sincerely doubt that APFS has caused I/O speed to actually drop, in fact from the WWDC demos (admittedly on a mac, but I can't imagine such a drastic deviation to iOS) performs many function at a breathtakingly faster speed.
Perhaps there is a bug in 10.3 itself (not related to APFS) that is causing the issue? I guess we'll have to see but this one is kind of hard to figure out without being able to peek under the hood you know?
I still keep my 6S on 10.2 and will wait to see how this goes...
Do you think that 10.2 is still faster than 10.3, despite synthetic benchmarks..?
Regardless of I/O benchmarks, my SE feels a lot faster on 10.3. It might be the Antutu app.
same here, also on a SE. And with beta 5 (at least, may have been since a beta before 5) the 3D Garden test results are also down.Hello all,
See attached a picture of the I/O performance in 10.3 vs 10.2.1
So in 10.2.1 the SE I/O speed was getting 13348, and in 10.3 it's 5875??
That's a huge drop in I/O performance.
Can anyone else run Antutu and confirm?
Thx
D
Hello all,
See attached a picture of the I/O performance in 10.3 vs 10.2.1
So in 10.2.1 the SE I/O speed was getting 13348, and in 10.3 it's 5875??
That's a huge drop in I/O performance.
Can anyone else run Antutu and confirm?
Thx
D