← Back to context

Comment by Kabukks

11 years ago

Holy CPU time! That site consumes 100% of my CPU (presumably 100% of one core) whenever it is in the front tab (Firefox/OS X).

Anyone else experiencing that or is it just my laptop running wild?

7 comments

Kabukks

Reply
cmorgan31  11 years ago

You'll see similar resource consumption when using event listeners tied to the mouse movement. It's generally not noticed by the general populace, but gives every developer a pause. The page does seem to struggle at times.

  • 72deluxe  11 years ago

    Very informative, thanks. In native land we can listen to mouse motion but it is more CPU friendly to have a timer and poll the mouse position periodically, particularly if the location of the cursor causes further processing (like working out what data to display in a popup hint). The good thing with the mouseEnter / mouseLeave is that you can stop the timer and only restart polling when they enter again.

    Is there a way of doing this on web pages or is it really still just callbacks for mouse motion?

serve_yay  11 years ago

It's like Myspace and Tumblr barfed all over Businessweek. I opened the article in Firefox with the mobile-emulation feature turned on. Because good god almighty this thing is a trainwreck otherwise.

jarek  11 years ago

Interesting, I was able to read the article just fine on my 2011 Kobo touch. 800 MHz ARM Cortex A8 and whatever Webkit was around in early 2011. The border animations are off but all the text and plain images work.

Whatever effects they're running, they did an impressive job with graceful degradation.