I am moving 10,000 small div elements in a css3 experiment from the top of the browser viewport to the bottom. For this test I use 2 different approaches:
- With GPU acceleration using
translate3D(x, y, z)or
- No GPU acceleration by simply adjusting the
topproperty in css
Using NO hardware-acceleration runs fairly smooth on Google Chrome.
If I enable hardware-acceleration performance becomes a lot worse. It’s so bad the boxes aren’t even spread out evenly anymore:
With GPU/Hardware acceleration:
Without GPU/Hardware acceleration:
Why is that so? Shouldn’t using the GPU improve performance?
My hardware used for test
- Apple Macbook Pro 15″ 2015 Model
- CPU 2,8 GHz Intel Core i7
- 16 GB RAM
- macOS Big Sur 11.2
Update (2014-11-13): Since this question is still attracting attention I’d like to point out that the problem itself still seems to exist although the mentioned stuttering might not be visible anymore in the provided demo on modern hardware. Older devices might still see performance issues.
*Update II (2021-02-17): The problem still persists but you will have to increase the number of boxes being moved in the demo based on the hardware used. I changed the UI of the demo app so you can now adjust the number of boxes moved to create a stuttering animation for your specific hardware. To replicate the issue I recommend to create enough boxes to see stuttering with GPU/hardware acceleration enabled. Then tick off the box and run the test again without acceleration. The animation should be smoother.
I always add :
-webkit-backface-visibility: hidden; -webkit-perspective: 1000;
When working with 3d transform. Even “fake” 3D transforms. Experience tells me that these two lines always improve performances, especially on iPad but also on Chrome.
I did test on your exemple and, as far as I can tell, it works.
As for the “why” part of your question… I don’t know. 3D transform are a young standard, so implementation is choppy. That’s why it’s a prefixed property : for beta testing. Someone could fill a bug report or a question and have the team investigate.
Edit per August 19th 2013:
There’s regular activity on this answer, and I just lost an hour finding that IE10 also need this.
So don’t forget :
backface-visibility: hidden; perspective: 1000;