"Amdahl's Law tells us that even with an infinite number of cores, an application that is 50% parallelizable will get only a 2x speedup over a single-core design."
The key words are "an application." There are often multiple applications vying for CPU cycles, all running at the same time. So in fact, I can show how a quad-core processor shows up as only 25 percent busy, or slightly more than that, when the same app running on a single core eats up 100 percent of CPU cycles.
I've read, though, that memory buses of today show no improvement beyond what you can eek out of an 8-core processor. The problem being choreography, in essence.
Many application used all day contain a damn lot of tasks that can be performed in parallel. Just take an editor frame as example: rendering, spell check and syntax or grammar check can be performed in seperate threads.
The fact most application are designed with a single core in mind does not imply, the application does nit contain paralellism.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.