3 ms·
The problem with SVG animation is it seems to be abnormally resource intensive. I noticed it on a project I worked on recently -- simply pulsing a few <circle>s
by deergomoo 8y ago
The problem with SVG animation is it seems to be abnormally resource intensive. I noticed it on a project I worked on recently -- simply pulsing a few <circle>s larger and smaller pegged a CPU core at a constant 40% on my work machine. Indeed, opening your (very cool) 404 page shows a constant 30% CPU usage.
Fine for a 404 page which people are unlikely to stick around on, not fine for a screen that someone is going to spend a significant amount of time on.
- Izkata 8y agoMy Firefox jumps from about 6% to 10% on that page... Noticeable, but not nearly as bad as you're seeing.
- tigershark 8y agoHow many cores do you have? If you have 8 it is scarily close to 100% for a single core.
- dasyatidprime 8y agoWhat browser/OS/hardware configuration is this? I have never observed such an effect before.
- pcwalton 8y agoI'm working on speeding this up via the Pathfinder project, for Firefox. :)
- tribby 8y agoawesome - I enjoyed reading up on your work! stuff like this makes me wonder if variable fonts will become a popular method for animating certain things on the web (maybe in the context of UI kits like font awesome, ionicons, etc). it still kind of blows my mind how quickly we all moved to abandon adobe flash once HTML became viable. I'm not a fan of the attack surface that flash presents, but in retrospect, especially thinking about the hardware I was using 15 years ago, it almost seems like advanced alien technology when contrasted with the state of vector animation on the web today.
- polskibus 8y agoDo you know by any chance if support for new SVG standard will ever land?