Qualcomm Says Eight-Core Processors Are Dumb
itwbennett writes "Following rival MediaTek's announcement of plans to release an eight-core processor in the fourth quarter, Qualcomm has declared eight-core processors 'dumb'. 'You can't take eight lawnmower engines, put them together and now claim you have an eight-cylinder Ferrari. It just doesn't make sense,' Qualcomm's senior vice president Anand Chandrasekher said, according to a transcript of his comments to Taiwan media provided on Friday. Asked whether Qualcomm would one day launch its own octa-core processor, Chandrasekher said, 'We don't do dumb things.'"
Fuck everything, we're doing five blades.
http://www.theonion.com/articles/fuck-everything-were-doing-five-blades,11056/ ...and then someone made one with five blades, and it's better enough that people will buy it.
Hail Eris, full of mischief...
E pluribus sanguinem
eight core processors are dumb. though not for the reason he gave. they are dumb because nothing supports 8 cores, so 99% of the time, the extra 2-6 cores are totally wasted. if the software would catch up to the hard ware, we might see more use in 8+ cores
...but every time some company says something is dumb, this usually means one of three things:
1) Our competitor has too many patents so we can't make it
2) We can't reach the quality/price of our competitor or
3) Not the product is too dumb, we're just too dumb to produce it.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
And my virtual machines say, "Shut your pie hole, Chandrasekher."
If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens?
To put a witty saying into 120 characters, jst rmv ll th vwls.
Software that's single-threaded, no it doesn't benefit from more cores. But modern heavily-multi-threaded software can benefit. More cores means more threads can execute simultaneously, and if the workload's heavily parallelized you can get it done quicker. No, you can't get a supercar engine from 8 lawnmower engines. But if I have a truckload of boxes to move into a warehouse, it'll go twice as fast with 8 normal guys who can carry 1 box per trip each than with 1 really strong guy who can carry 4 boxes per trip. And when you consider that with CPUs the really strong guy isn't 4x as strong as the normal guys, he's more like maybe 50% stronger, the performance improvement for the 8 guys is even better. Assuming of course that you've got individual boxes to move. If they're all packed up inside a shipping container and you have to move the entire shipping container, then yeah you need 1 guy with a crane rather than 8 guys by hand. Modern software, though, is leaning towards breaking things down into small chunks that can be dealt with in parallel, so octacore CPUs are going to help and Qualcomm's living in the 90s.
Add a scoop, spoiler, neon trim and a fart can on the exhaust. Mowed in sixty seconds.
It is if your software can only address 640K. You don't add 8 gigs of RAM to your 8088 PC.
It is the fallacy behind the Pi. I have 4 of them and use them for everything. However I'm not interested in taking significantly limited resources and programming against that in an effort to build my skills. I want the power. So a quad core Pi with SATA, Wifi, 2-4 GB of RAM, using just 5 watts of power, and much more, for $20.00 is just fine by me. I'd use that too. So would every other developer. I'm sure current developers hate the limitations of some of the devices out there.
You can lead a man with reason but you can't make him think.
You know what multiple cores are great for, that a very large segment of the population does? Image processing. A very large subset of things you can do to images responds very well to slicing an image into [#ofCores] slices, and then whacking away at them in [#ofCores] parallel.
I write SDR software, that kind of programming can really benefit from multicore hardware too. At least, the way I write it, it does.
Anyway, I think ol Qualcomm is lacking a certain basic understanding of what multicore architecture brings to the table. Er, phone. Desktop. Tablet. Whatever.
But that's ok. Manufacturers that remain mired in the past fall to their competitors and so self-select themselves out of the game.
I've fallen off your lawn, and I can't get up.
I thought the reasoning behind multiple cores was so you could power off the ones you're not using. It's not that you're taking 8 lawnmower engines and turning them into an 8 cylinder Ferrari engine, but you're putting 8 smaller lawnmower engines on your lawnmower so instead of using the big 80HP engine when you're just trimming a narrow stretch of grass, you only need to power up one 10HP engine while the rest of them remain powered off. If you're cutting wider stretch of grass, you can use 2 engines, etc. So you save energy by only using as many cores (engines) that you need for the task.
Nah, you're just doing it wrong. Take list of names, then mark as, or make sublists, the main list with [#ofThreads] of alphabet, which involves no more than looking at the 1st character and using that to target a list - a jump table of [alphabet] size would allow doing this in one instruction. There's a need to make sublists anyway, so creating them in a "deal the deck" way incurs no significant overhead. Hand off to multithread sort, result comes back in already completely in order, just link the new list ends in your [#ofTHreads] order and you're done.
There are certainly hard-to-parallelize problems, but alphabetizing a list isn't one of them.
I've fallen off your lawn, and I can't get up.