- 09-17-2012, 02:02 PM #1
In my boredom I re-listened to the WP8 Keynote from June 2012
One of things Joe B talked about in the 8 platform announcements was the support for multi-core processors
As I listened again, I noticed that he said WP8 kernel could (shared kernel with desktop and servers) run on 64 core machines but that didn't mean it was ready.
As a matter of fact, around the 12:00min mark he says
The work we have been doing on WP8 has been focused on dual-core for this fall and we are doing all the optimization on dual core first for WP8 devices...
* quad-core+ WP8 software will not be not ready in 2012
I think this rules out any quad-core HTC devices being released in 2012 as the current version of WP8 has only been focused on dual-core devices.
I do hope that MS adds support for quad-core devices ( for the spec crowd and subsequent bragging rights ) early 2013 as Qualcomm is now ready to release their quad-core processors
Snapdragon™ Processors | All-in-One Mobile Processor | Qualcomm
The LG Optimus G uses this processor.
Again, I expect WP8 to run smoothly on a dual core devices, but I don't want WP8 to limit the OEM from releasing their latest and greatest devices ( like 2010,2011) because of the limitation of the OS
- 09-17-2012, 02:21 PM #3
I created this post because of the rumors of some HTC devices having 4 cores, the OS not currently being ready to support 4 cores makes me question if their will be a HTC One X(+) equivalent.
Finally, the big guns: "Zenith" is expected to have a 4.7-inch 720p Super LCD 2 with the same 8-megapixel sensor as the Accord, 42Mbps HSPA+, and an unnamed quad-core Qualcomm Snapdragon
09-17-2012, 04:23 PM #4
- 390 Posts
There are problems with quad-core processors and the US version of LTE. That's why both the HTC One X and Samsung Galaxy S3 are quad-core for their international versions but dual-core for their US models.
Microsoft is very US-oriented, so if it doesn't work for the US market, they may not be doing it at all.Loyal first and foremost to a carrier (US Cellular). Open to either a Lumia 820, or an HTC 8X, or an Ativ S.
- 09-17-2012, 04:39 PM #5
- 09-17-2012, 06:00 PM #7
C'mon guys. How many times do we need to go over this:
- keeping the WP8 OS lean and mean
- preserving Microsoft's ability to deliver OS updates directly to our devices without OEM involvement (a long standing goal they have so far failed to achieve but are trying to complete the legal foundation for)
- giving developers the ability to optimize their apps for a specific hardware platform
Any one of those things is more important than the meaningless core count number on the spec sheet, which brings me to my recommendation that you read this thread on that subject (a long read). In that thread I attempt to explain why, on mobile devices, high-end dual-core CPU's will almost always run your apps faster than high-end quad-core CPU's. All the important players get this:
WP8 devices = dual-core
iPhone 5 = dual-core
Upcoming Samsung Galaxy S4 = all dual-core (everywhere in the world)
The question is will consumers ever catch on?
Qualcomm is currently the only company offering a SoC with an integrated LTE receiver (Snapdragon). Building a competitive LTE device with any of the competing non-integrated offerings is simply not a viable option (due to battery drain). However, that SoC from Qualcomm is only available in a dual-core variant. That is the only real reason U.S. LTE devices aren't shipping with quad-core CPU's.
10-01-2012, 11:47 AM #8
- 240 Posts
In 2-3 years when Quad-Core Mobile Processors (Smartphones) are widely prevalent, I expect you to lead the charge against Hexacore devices of the same type. Because surely we can't have our mobile computing devices breaking boundaries, getting smaller, or becomming more energy efficient.
1912 Forever!! That is all.
- 10-01-2012, 12:19 PM #9
Though I get what the OP is saying, I also might like to add, quad-core isn't the best thing happened to phones, yet.
Buried here somewhere, I took have a thread of dual core optimization. The damn apps and everything that makes use of it needs to be OPTIMIZED to make use of it..
If ultimately, your apps are gonna use just ONE core, you can happily rent your other cores to homeless teenagers and make some money out of it.. :P
Sent from my RaZr HD.
- 10-01-2012, 12:33 PM #11
What exactly do we need four cores on a cell phone for exactly?
As someone who is pretty engrained in the PC hardware world both personally and professionally, this makes no sense to me. I want a fast core clock on a dual core. A quad core isn't going to do much else on a device with limited multitasking. And 99% of the applications out there are going to utilize two cores.
- 10-01-2012, 12:43 PM #12
Same was said when AMD introduced DC and intel was still using P4 SC at higher clock. Was quite apparent which direction was better as intel does not have an 8ghz SC P8 now, they have Multi core chips.
Why do you have more than 640k memory anyway?
- 10-01-2012, 12:53 PM #13
Huge difference. That was utilizing the ability to split application load into multiple cores, or not. Here we are talking about splitting it between 2 and 4. Which is pretty much useless with current smartphones with limited multitasking. It makes more sense for devices like tablets.
10-01-2012, 01:12 PM #14
- 453 Posts
I don't think anyone is suggested than a quad core A15 (or Krait) would be a bad thing. The annoying part is the people that assume that 4 is better than 2 and that means a quad core A9 is better than a dual core A15 (or Krait).
I would love to see a quad core WP8 phone, but being jealous of the CPU performance of the Exynos or Tegra 3 is silly.
- 10-01-2012, 01:19 PM #15
I view the fascination with quad core to be based mostly on the fact that Android is so poorly designed and optimized. A dual core device running a well designed OS can still run circles around quad core running a bad OS. The current situation in tablets is a good example. Even the fastest quad core Asus tablets have some degree of lag since they are essentially hamstrung by the OS. My BlackBerry playbook with a 1 ghz dual core processor is laughably smoother than my Transformer Prime running Android 4.1. I expect people will see a few quad core Android phones in the relatively near future, being touted for their amazing processing power. In real life, they will be just about as fast and smooth as a new iPhone or Windows Phone 8, and will also have the battery life that goes along with shoving a quad core in a phone....
10-01-2012, 01:23 PM #16
- 266 Posts
As far as I know, the latest S4 quad cpu does have an LTE modem on it, it just took them longer to work out the issues so it couldn't be done for this generation
a5cent is right and his thread is spot on, first of all look how well WP runs on a lumia 710, much better than a lot of mid range droid devices with better specs - that should make you think.
I have a intel i3930K 6 cores 12 threads and 95% of the software doesn't or can't utilise all six cores effectively, the amount of time I watch task manager and curse all 12 threads sitting there chugging away using 8% of each thread.
Sometimes the difference between that and my i5 cpu is negligible.
There is no point of a quad core cpu until software developers are ready to use it, they aren't on android yet, and they aren't on WP8 - Id swap quad core cpu for optimised dual core OS and better battery life anyday of the week
Like I said, look at the 710, it doesn't feel laggy at all - the proof is in the pudding
- 10-01-2012, 01:31 PM #17
It reminds me of my co-worker who opted for a slower clock speed i7 over an ivy bridge i5 because the i7 has hyperthreading.
He has yet to use any application that utilizes hyperthreading.
A silly world we live in.
- 10-01-2012, 05:26 PM #19
Hasn't anybody else noticed that quad-core CPU's aren't even that common on desktops yet? Just because you see 4 processors (thanks, hyperthreading), we're still dominantly dual-core.
Why, then, do we obsess over quad-core phones? Why do we expect that a quad-core phone should somehow be cheaper than a quad-core desktop system? It's ludicrous.
I'm not against it, I'm a tech guy for crying out loud I WANT it, but I'm realistic too.
- 10-01-2012, 09:00 PM #20
Here's the thing... price is only related to die-size. Nothing else. Die-size is a function of the number of transistors and manufacturing technology (node size):
All CPU designers are given a set of constraints they must consider when developing their CPU's, but the constraints server/desktop-CPU designers and mobile-CPU designers edge up against first, well, they differ:
server/desktop-CPU designers = hit die-size constraints first
mobile-CPU designers = hit power & thermal constraints first
The die-size constraint is basically a function of the highest acceptable manufacturing cost per SKU (bigger die-size = higher manufacturing costs). These "huge" CPU designs that target the largest possible die-size end up being that generations flagship CPUs. From there, server/desktop-CPU designers cut the number of cores and reduce cache sizes to get CPUs that use less transistors which result in smaller dies and lower manufacturing costs. From this approach we currently get server/desktop-CPU's ranging from $100 up to $1000 which integrate between 500M and 1.5B transistors and two, four or six cores (eight cores in special cases). That is why many relate less cores to cheaper prices, when it is actually about die-size.
However! Mobile-CPUs hit their power and thermal limitations long before getting anywhere close to the limits of what can be cost effectively manufactured. So, the number of power sucking transistors mobile-CPU designers can cram onto a die are far fewer, which means the die-size can be much smaller, resulting in much lower manufacturing costs. From this we get products ranging from $10 up to $30, which includes not just the CPU but the entire SoC (GPU and a whole host of specialized co-processors, sometimes even including circuitry related to radios).
So, the mobile-CPU designer gets limited to a a much smaller die-size (remember, transistor count, manufacturing technology and die-size are all proportionally related). Assuming revolutionary advances in battery technology aren't just around the corner (seems unlikely), that die-size isn't likely to change in the foreseeable future. We will get advances in manufacturing technology, giving us smaller transistors that suck less juice, but those advances will instantly be invested into CPU's with a proportionally larger number of transistors leading to more powerful CPU's on roughly the same die-size as before. Because the die-size will remain similar, so will SoC prices (for the foreseeable future).
Hitting different constraints first is why server/desktop-CPU and mobile-CPU design is fundamentally different.
And yes, that is also why high-end dual-core and quad-core smartphone SoC's will also be very similar in price... same number of transistors using the same manufacturing technology = same die-size = same price
Last edited by a5cent; 10-01-2012 at 11:15 PM. Reason: Spelling
- 10-01-2012, 09:17 PM #21
In the words of Spock, "I do not dispute it. I merely state that it's wrong."
You can argue tech specs all day long (and I've been doing IT work 20 years) but it doesn't change the fact that it's not a relevant spec yet... desktop or mobile.
- 10-01-2012, 10:12 PM #23
- 10-02-2012, 07:08 AM #24
Same reason ARM is moving to multi core is the same reason x86 architecture moved to multiple cores. It was easier to get more performance from more cores than from clocking the CPUs to light speed. Athlon 64 X2 practically destroyed the P4EE clocked at 3.73ghz.
- 10-02-2012, 07:23 AM #25
Take your 6 core and transcode a video. Or, do a rendering in strata, or play around with a 500mb image in photoshop. Then you will love your 12 HT cores. If you do not do any of that stuff at home, then you wasted your money on your shiny new chip. Upgrading from SB to IB is pretty much a waste for gaming and surfing but I am sure you realize that.
Watching the Nokia phone app that edits video and pictures in real time, that could very very easily work faster with a quad core. So look at the software that Nokia is making with DC, what do you think they could do with a hex core ARM?