News for hackers. Stuff that matters.
Re:Seriously.js by joezydeco on Wednesday June 05, 2013 @04:45PM (#5828481)
Wow, I've never seen all 4 cores in my machine simultaneously spin up to 90% before. Nice trick.
Re:Seriously.js by Tomdarkness on Wednesday June 05, 2013 @04:47PM (#5828495)
Hm, that is strange. It does not even tax my CPU enough to kick it out of its lowest speed state, let alone tax any of the cores.
Re:Seriously.js by mischanix on Wednesday June 05, 2013 @07:04PM (#5829249)
That's because all the work here is being done through WebGL shaders. Your parent experienced a software fallback, I guess.
Re:Seriously.js by diydsp on Wednesday June 05, 2013 @05:31PM (#5828755)
Intel announced a year or so ago they could JIT compile javascript and run it on their GPU. Maybe that's why?! If so, welcome to the bold new age of GPGPU and AMD's HSA... :)
Re:Seriously.js by scott_karana on Wednesday June 05, 2013 @06:38PM (#5829132)
Likewise, 5-7%, but I don't have a nice new machine like you do.

Core 2 Quad Q9950 and an nVidia Geforce 8800 GT 512MB.

Re:Seriously.js by joezydeco on Wednesday June 05, 2013 @05:29PM (#5828749)
That's interesting. What kind of CPU?
Re:Seriously.js by Tomdarkness on Wednesday June 05, 2013 @06:34PM (#5829111)
Intel 3930k:

http://i.imgur.com/OF58RZl.png

After the peaks when it is flat at around 3% is when it is playing.

Re:Seriously.js by atwebb on Wednesday June 05, 2013 @04:47PM (#5828493)
You must be a better programmer than me.
Re:Seriously.js by chacham15 on Wednesday June 05, 2013 @04:59PM (#5828577)
If you write single threaded applications you cant go above 1 core and so will never hit this mark :)
Re:Seriously.js by astrodust on Wednesday June 05, 2013 @05:20PM (#5828679)
fork disagrees.
Re:Seriously.js by gnaritas on Wednesday June 05, 2013 @07:42PM (#5829429)
As does pipe.
Re:Seriously.js by knome on Wednesday June 05, 2013 @08:44PM (#5829664)
Rapidly cycling the processor affinity tries its best.
Re:Seriously.js by gnaritas on Thursday June 06, 2013 @12:20PM (#5833346)
Say what?
Re:Seriously.js by atwebb on Thursday June 06, 2013 @12:00PM (#5833210)
It was weird timing because I was working on a multi-threaded application that was murdering my server (expected) when I made the comment.
Re:Seriously.js by corysama on Wednesday June 05, 2013 @06:08PM (#5828992)
Hmmm.... My 2.5Ghz Core2 Quad is sitting at 15-20%. Compared to watching the vid on youtube at 5-10% utilization.
Re:Seriously.js by RyanMcGreal on Wednesday June 05, 2013 @08:43PM (#5829661)
I'm running an i5 processor, and when the video was playing my cores jumped from the 5-10% range (background stuff I've got running) to the 25-40% range.

Interestingly, just switching from the demo tab to this HN tab (FF 21 on Ubuntu) drops the cores to the 10% range. They jump again when I switch back.

Re:Seriously.js by aceperry on Wednesday June 05, 2013 @06:56PM (#5829204)
LOL, my old core2 duo has both cpus running over 80% on Ubuntu with a GeForce GTX260. But when I click on another tab, with the video still playing on a non-visible tab in Chrome, the cpus drop to around 20%. When I click on the video tab again, the cpu ramps up to the 80% mark again. Neat trick.
Re:Seriously.js by brianchirls on Thursday June 06, 2013 @01:28PM (#5833781)
That's the nice thing about requestAnimationFrame. It's smart enough to not waste time updating if you're not looking at it.

As for 80%, umm... video driver issues? :-(