4 ms·
I'm also on a 4S and it doesn't feel laggy to me. In particular I'm feeling much fewer "hiccups" as new data comes in than I do with Apple Maps. Now, at the sa
by shock-value 14y ago
I'm also on a 4S and it doesn't feel laggy to me. In particular I'm feeling much fewer "hiccups" as new data comes in than I do with Apple Maps.
Now, at the same time, it does seem to be locked at 30fps rather than 60 (as in Apple Maps). So it's not quite as silky smooth in that respect, I suppose, but it'll also drain battery more slowly.
- acchow 14y ago> but it'll also drain battery more slowly. Doesn't really work that way, especially in a triple-buffering system.
- shock-value 14y agoCan you elaborate? If you are drawing to the buffers at half the rate (and correspondingly swapping them out at half the rate), how would that not be easier on the graphics processor?
- acchow 14y agoTriple-buffering allows for arbitrary relative speeds. The result is, you draw to the buffer as fast as you can in total disregard of the actual refresh rate. So they're both at "100%" CPU/GPU, but that simply isn't enough for Google Maps.
- shock-value 14y agoI think Google actually locked Google Maps at 30fps though. In other words, I don't think it is actually drawing as fast as the processor would allow, were Google to remove that lock. Otherwise I'd expect to see more fluctuation in the framerate of the app, especially when there isn't much detail on the screen (similar to Apple Maps, which is obviously not locked to 30fps).