The last official position I've seen is that it may launch in 2017, but I've only seen it mentioned in a data center context--where Qualcomm is making moves as well.What about K12, was not canned right?
The high end ARM cores already are way above Atoms in performance in my opinion and experience.
The interesting question is whether they will also recompiled Win32 API apps, not just emulated ones.
High end ARM cores are still low end compared to Intel Core CPUs, Apples CPUs excepted (but Apple isnt in the chip merchant business).
Cheers
With 8 cores versus 2 in multi-threading guess who will be the fastest.
The fast dual core will. You put too much confidence in multithreading.
Look at iPhones, hands down the best hardware in the phone segment.
Cheers
Why then PS4 and XBOne have 8 cores instead of 2 faster ones (and they are x86) ?
Because consoles are special purpose machines, where you need maximum performance/$ and maximum performance/Watt. Console games typically have one or two compile targets, allowing you to use CPU specific intrinsics and utilize specific system architectural knowledge (cache hierarchi, memory capacity/structure etc. )
For apps going to a plethora of devices, mobile or otherwise, that's just not the case.
Cheers
Yeah, but almost none of the threads/processes are active (is in a run queue). As I type this, I have 1428 threads on my Windows 10 PC and CPU utilization is 1-2% (6core, 12 context CPU).Phones are like tablets and pcs devices that run a large number of processes in parallel.
Yeah, but almost none of the threads/processes are active (is in a run queue). As I type this, I have 1428 threads on my Windows 10 PC and CPU utilization is 1-2% (6core, 12 context CPU).
Modern apps utilizes async tasks to a large extent. Each active async task has its own thread. If you have a computationally heavy app you might use lots of cores, but in most apps you use async tasks to avoid blocking the main thread (which runs the GUI). Android and IOS both mandates network access be done in async tasks. So you spawn your task and send your network request, - in a matter of microseconds, the thread then waits 100 miliseconds for the response, and resumes.
You can have many tens of async tasks in flight with near zero CPU usage. This can cost power in a many core SOC, because you have plenty threads and the scheduler fires up all cores, then they mostly sit idle, but not idle enough to be powered down.
Look at the graphs on this page from Anandtechs multi-core investigation article. Notice how many of the cores in either the LITTLE or big cluster are active, and notice how CPU usage is only 30-40% and how cores are clock gated instead of power gated (especially true for the big cores). You have four cores running, but two cores could have done the same work, - at the same clock frequency. As a consequence, power is wasted.
Cheers
Scanning the conclusion in the Anandtech article they actually agree with me?
Have you seen any themes, all the screenshots just show wallpaperand I don't like the themes at all.
that sounds more correct, as of now they are just screenshots that change a bit some colours of the interface, and that's itHave you seen any themes, all the screenshots just show wallpaper
That's all a windows theme is. A collection of wallpapers and a UI color selection.that sounds more correct, as of now they are just screenshots that change a bit some colours of the interface, and that's it