4 ms·
Attention: It nearly flipping fried my CPU. But awesome site. Tested On both Safari and Chrome on macOS. 100% CPU usage when scrolling. Edit: On WOW, from th
by ksec 6y ago
Attention: It nearly flipping fried my CPU.
But awesome site.
Tested On both Safari and Chrome on macOS. 100% CPU usage when scrolling.
Edit: On WOW, from the comments I decide to try it on my iPhone 11. Ultra Smooth Rendering with Music ( which wasn't even playing on my Mac ). And my phone isn't even warm after a minutes of playing around. Amazing
Which makes me wonder. Why?
- aikah 6y agoIt was pretty smooth actually, and I'm on a Intel N5000 with 4 gigs of RAM. Not sure it uses WebGL or CSS, but the performances are rather good.
- thitcanh 6y agoIt’s kinda ridiculous that this happens. It’s not like it’s graphic intensive. Why would it warm up any GPU of this decade?
- bruce343434 6y agothe power of javascript
- pm90 6y agoAre you powering a large monitor? I would guess the graphics doesn’t scale well with screen size.
- fireattack 6y agoIt must be something Mac specific. It runs very smoothly on Chrome + Windows with a dated computer.
- ksec 6y agoYes, interesting all the comments suggest it is Mac specific and not browser specific. Tested again on Firefox Mac, same thing. Very strange.
- jeroenhd 6y agoPerhaps this has highlighted a problem in the Metal render backend? Firefox generally sticks to the OpenGL standard (using ANGLE as a workaround where only DirectX is available on Windows) whereas Apple has their own APIs. For example, Firefox seems to make use of the more proprietary Core Animation API got certain tender tasks, which no other OS needs special code for. If the Core Animation API or the code calling it has a bottleneck, you'll only see this problem on macOS. It could also be a consequence of the way Apple optimises their laptops. On my phone and laptop, the websites hammers one single core (about 87% CPU usage on my laptop here). Apple has optimised their CPU power curves (on Intel, at least) to turbo high and turbo quickly, making actions like loading a website and opening an app nice and snappy. The design of the laptops doesn't allow these high turbo speeds for more than a few seconds, so CPU performance drops after a few seconds. For most use cases that's fine, but I can see a website like this running into that problem. Same thing is happening on Chrome, which is snappier for me but also more CPU intensive. Edit: actually, after trying Firefox on my hackintosh (7700k, gtx1080), it's more likely to be hardware related. I have no trouble whatsoever with the website on any browser on my desktop, even the outdated copy of Safari works fine.
- starfallg 6y agoOn a 2020 MacBook Pro (Intel) and working fine.
- ComodoHacker 6y agoIt hogs my latest Firefox into being almost totally unresponsive. It takes minutes after closing a tab to recover.
- foxhop 6y agoWorked amazing on Firefox for Android.
- throwaway2037 6y agoWoah, you are right! I just checked my Chrome task manager (Shift+Esc on Linux). It is never less than 50% CPU at top of page in 3D mode. If I scroll, it jumps to > 100% CPU! The tab is using 250MB of RAM. And to think I am working on a ridiculously over-powered workstation w/ 3.8 GHz cores & 4K screens!
- kizer 6y agoAll the bloat of the many abstraction layers. Also maybe (some of) the rendering is happening in the CPU; didn't check to see how they did it.
- ArtWomb 6y agoYes, I experienced something similar. Issues on certain devices / browser combos. But smooth animation on others. I'd like to delve in deeper when I get time to investigate. But generally Web Audio API "sprites" play on the main thread and can lead to sync issues. ThreeJS uses requestAnimationFrame which can also yield vast FPS differences across devices. Developers can calibrate rendering per device, but its a lot of procedural code. Better to just do what Yamauchi has done: get it in a playable state and make a splash ;)