13 ms·
M1 Icestorm cores can still perform well
- webmobdev 5y agobig.LITTLE Processing: Defining the Future of SoC Architecture - https://www.samsung.com/semiconductor/minisite/exynos/newsroom/blog/biglittle-processing-defining-the-future-of-soc-architecture/ https://www.samsung.com/semiconductor/minisite/exynos/newsro... With this CPU design some cores are optimised for performance (at the expense of using more power) while some cores are optimised for efficiency (using the least power at the expense of computing performance). This makes sense for laptops and smartphones, as it can save power and thus run longer when being powered by batteries. But (in my opinion) not for Desktop PC's where most people care more about computing performance than saving a few watts.
- m_eiman 5y agoSaving watts means lowering fan RPM, meaning less noise. And that's a big priority for many.
- n1000 5y agoAlso, aren’t desktop CPUs constrained by thermal load at some point or can we use ever bigger coolers? Personally, I find it almost obscene that my desktop PC consumes roughly as much as a good old incandescent lightbulb (60+W) while idling. My laptop uses as much under full load.
- Synaesthesia 5y agoYour PC uses 60w idling? Is that with screen? It's not too much in that case. CPUS and GPUS have gotten a lot better at idle power consumption, and PSUs are also quite efficient these days.
- n1000 5y agoAs discussed here [1], a fairly beefy Ryzen/RTX setup is often found idling around that number. [1] https://hardforum.com/threads/killawatt-owners-whats-the-idle-power-consumption-of-a-new-ryzen-system.2002676/ https://hardforum.com/threads/killawatt-owners-whats-the-idl...
- namibj 5y agoDownvolt and downclock your RAM when possible. Turn off VRM phases when not needed (also on the GPU; RAM should be handled properly already on it). Allow package-C6. Turn on PCIe power saving stuff. There is a bunch of stuff that mildly hurts performance and greatly improves efficiency in intermittent workloads, by letting hardware sleep/power-off when not needed.
- Roritharr 5y agoNot only that, i'd prefer to have a small amount of ram and cpu to be running 24/7 for always-on features that I'd love to have my PC doing. I don't like having to run a PI for some stuff just because i don't want my huge tower running all the time, it would be really neat if it could run at anything between 5 - 600W, not sure though if the PSUs would be able to offer that range.
- webmobdev 5y agoI guess so - I really don't care about the fan noise (I'd rather PC makers think more about sound proofing for that rather than reducing fan RPM thus reducing performance).
- Synaesthesia 5y agoMost of the time your PC isn't working hard, and it makes sense to use lower power cores to perform basic tasks.
- webmobdev 5y agoI understand that perfectly. But how willing are you to sacrifice performance for that, is my point. There's a reason why CPU makers focus on building faster chips - that's what people care about most on Desktop PCs.
- Synaesthesia 5y agoYou don't need to sacrifice performance since CPUs step down automatically. For a hybrid design they only use the smaller cores for less demanding tasks. In fact this design gives a perceived increase in performamce as the author has written about.
- webmobdev 5y agoOfcourse you are sacrificing performance when you put slower cores alongside fast cores, instead of using all fast cores only. And for what - ARM cpu cores already are very efficient. So saving a few more watts with the slower cores, at the expense of performance (faster cores) isn't a worthwhile tradeoff when you are doing some cpu intensive task on your desktop. Saving a few extra watts matters on phones / tablets / laptops because you can use it longer on battery.
- simondotau 5y agoI'm not sure that you could make a case for this not making sense in a desktop computer, as everything is ultimately a trade-off. It's fairly clear that the Icestorm cores represent a performance gain in terms of performance per watt, but also die area. The four Icestorm cores and their support infrastructure takes up about the same physical space as one Firestorm core with its support infrastructure. I doubt that an M1 with five Firestorm cores would perform as well as the eight cores we did get.
- webmobdev 5y agoMy case for having 8 fast Firestorm cores instead of 4 fast + 4 slow cores is simple - the majority of Desktop PC users don't care about sacrificing performance to save a few watts. When a PC is running slow because of a cpu intensive task, nobody is going to appreciate that it is saving a few more watts. And from the figures in the article, it looks like 1 Firestorm core is very roughly equal to 2 Icestorm cores - Relative to their Firestorm times, Icestorms performed more slowly by: 190% running assembly language 330% running simd (Accelerate) library functions 280% running simple Swift 550% running ‘idiomatic’ Swift So 5 or 6 Firestorm cores could have matched the current 4 + 4 config (disregarding the valid point you made about the die area).
- nicoburns 5y agoThe rumours are that this year's MacBook pro's will feature an M1X processor with an 8 + 2 configuration which seems like it might well be a good tradeoff to me. The 2 small cores reduce context switching on the big cores making overall performance a lot snappier.
- Applejinx 5y agoI'm going to guess that if you could have 8 Firestorm, you will always be better off having 6 Firestorm/8 Icestorm. Always. In practical use. Even for the most isolated tasks there'll be enough 'maintenance work' for the system to do, in practice, that the pool of Icestorms will justify their real estate. If I'm mistaken, it'll be because there proves to be a maximum number of Icestorm cores for the 'maintenance work' that's called for: say if you had a 64/64 system, the idea is that maybe you get to a point where you can have 'too many cores' on the Icestorm side, wastefully so. But that assumes they play NO role in setting up the Firestorms to perform optimally. All this stuff, all this load balancing and assigning, isn't magically done by some GrandMasterCore, it's being worked out by the same CPUs that are benefitting from the load balancing. If you can use Icestorm cores to better set up and load balance the Firestorm cores, if you can burn unused CPU on the Icestorm side to optimize the Firestorm side… then there is NEVER a situation where you'd want the Firestorms to outnumber Icestorms. If that's happening then the Icestorms are doing some grunt work to clear a path for the Firestorms, and if you can burn more cycles to further optimize that, well…
- masklinn 5y ago> not for Desktop PC's where most people care more about computing performance than saving a few watts. Not for all workloads. Daemons and services don’t usually need much oomph, and being able to run them at double the efficiency and avoid them competing for resources with software which actually wants the higher power cores would be amazing: less context switching, less cache thrashing, less random variability, … Hell, it would also help make low-power software more reliable e.g. foobar and the audio output don’t need much but they need it. If something else is loading the machine to the gills they can get starved and audio will start breaking down.
- webmobdev 5y agoI do understand the pros and cons. My point was that it doesn't matter when you prefer peak performance vs efficiency on a desktop PC. I'd rather have 8 Firestorm cores on my PC, with one or two of these fast cores dedicated for the "lighter" workload even if it consumes a few more watts. When your desktop computer is slow, doing a CPU resource intensive task, nobody is going to appreciate that it is consuming less power - everyone will be cribbing about the slow speed.
- celrod 5y agoAssuming die area is the constraint, the choice is between 4 firestorm + 4 icestorm and 5 firestorm, because a firestorm core is 4x bigger than an icestorm core. Or between 8 firestorm and 7 fire + 4 ice (or 6 fire + 8 ice).
- Applejinx 5y agoI thought the idea was that not all processes are the same class of citizen. Some of 'em go to high performance cores, but some of them always get assigned to what's basically a second computer running in parallel and handling interface stuff or system management, typically a lot less powerful (though according to this article, far from helpless). In this way the CPU-intensive stuff never has to break its concentration by sullying its tiny processors with utility calculations, but keeping the observable system responsive (a much less demanding task) goes to the second, weaker computer, that's running as if nothing else is happening. So neither thing ends up being slow, because neither thing particularly has to be interleaved with the other. Source: I'm no CPU or SoC designer, but I own a Mac M1 laptop for the purposes of compiling open source plugins to the new machines, so I've done hundreds of XCode compiles on the machine, and lots of housekeeping work in Finder. None of it seems slow, by any metric or perspective.
- occamrazor 5y agoDepending on the specific workload, if the “slow” cores are more efficient per watt it may be preferable to have only a small number of “fast” cores for single-threaded applications and many slow cores. Or possibly vice versa if that’s not true. The M2 processor could be 4-big 64-LITTLE, or 16-big 8-LITTLE or some other combination.
- Applejinx 5y agoNot unthinkable. It depends on how the load balancing is, especially if the little cores are far from helpless on their own.
- pdpi 5y agoA small home server running 24/7 on low load mostly off of the small cores that can seamlessly ramp up to big cores for power when needed sounds exactly like the sort of thing you'd want.
- KuiN 5y ago> not for Desktop PC's Intel don't agree. They are using a heterogeneous architecture for desktop class chips in upcoming Alder Lake processors [0] [0] https://www.anandtech.com/show/16881/a-deep-dive-into-intels-alder-lake-microarchitectures https://www.anandtech.com/show/16881/a-deep-dive-into-intels...
- oarsinsync 5y ago> This makes sense for laptops and smartphones, as it can save power and thus run longer when being powered by batteries. But (in my opinion) not for Desktop PC's where most people care more about computing performance than saving a few watts. You're probably right about laptops and smartphones. I don't have a view on whether you're right about desktops, but I think it's probably not true for the big datacentre providers, who absolutely optimise for power and heat. If the only niche that doesn't care about power is the desktop, and desktops are absolutely a niche when compared to the total market of smartphones, laptops and datacentres, I suspect power efficiency is coming to the desktop whether you want it or not, whether it's a positive or not, if only because of economies of scale as far as chip development and production goes.
- webmobdev 5y agoYes, I realise that datacenters do care about power consumption too, and that is why they find the idea of a ARM server cpus so attractive. My point ofcourse was directed at home users of Desktop PC - I don't like the idea of sacrificing performance to save a few watts, when the ARM cpus are already very efficient. (I mean, when you are rendering a 3d scene, or encoding a video, or compiling a code, no one I know is going to appreciate the longer times it takes to execute these tasks because not all cores are equal).
- codetrotter 5y agoIf the author is here and able to do so I’d much appreciate if they would share the complete code for the benchmarking as a whole, so that others may use it for benchmarking other code in the same way :)
- simondotau 5y agoTLDR: Based on a single simple synthetic benchmark, the low performance "Icestorm" cores were shown to be as much as 52%—or as little as 18%—of the performance of the primary "Firestorm" cores. Highly efficient assembly showed the least performance drop whereas complex "idiomatic" Swift code showed the greatest performance drop. However the Icestorm cores also use substantially less energy so they are an efficiency win regardless. Plus they take up use significantly less physical space which is a large cost saving for the SOC part.
- Filligree 5y agoHow significantly less, I wonder? For my workloads it’d be an overall win to have more cores at that speed. The more the better; I’d cap out at maybe a a hundred or so. Obviously Firestorm is better, but a hundred-core desktop CPU at present seems… unlikely.
- maccard 5y agoAMD [0] would like a word. it's 64 cores but 128 with hyperthreading. [0] https://www.amd.com/en/products/cpu/amd-ryzen-threadripper-3990x https://www.amd.com/en/products/cpu/amd-ryzen-threadripper-3...
- Filligree 5y agoSo, not a hundred-core processor yet. I can’t use hyperthreading. It does give a 60% speed boost, but it’s also disabled in production so…
- shantara 5y agoI didn't realize map-reduce was so much slower than a regular looped multiplication, regardless of the hardware the code was running on.
- zozbot234 5y agoYes, that was weird for a language with such a high focus on performance. My guess is that the compiler couldn't inline the "idiomatic" operations and had to fall back on generic implementations, which will be painfully slow in Swift due to the overhead of being ABI independent. You could do all this in other languages too, but it wouldn't be the "idiomatic" choice during development; it would be clear that you're giving up on performance for the sake of flexibility.
- ChrisMarshallNY 5y agoI suspect that, for most cases, it won’t matter (not everything needs to be optimized -heresy, I know). But for some “inner loop” stuff, it could make a big difference. Another issue, is that visitors will hit the entire set; even when it is no longer necessary to continue. We can do some tricks to make subsequent visits shorter, but they’ll happen, nonetheless. This always bothers me.
- viktorcode 5y agoIt isn't slower per se. The 'idiomatic' and imperative part aren't equivalent; 'idiomatic' performs unnecessary work. The real problem is the existence of the overhead isn't obvious from the code.
- hajile 5y agoThat's an implementation detail. Consider JS. The builtin implementation is naive and chaining calls results in multiple passes over the array. Lodash is different. It uses an iterator internally, so chaining isn't much of a performance difference (just the overhead of the function calls which are probably inlined by most JITs anyway). I see no reason why Swift couldn't (or shouldn't) do this in a future version.
- kruxigt 5y agoIdiomatic Swift seems impressively bad? Is this the future in Apples eyes?
- sharmin123 5y agoHow Does A Hacker Hack A Phone? How To Avoid Phone Hacking?: https://www.hackerslist.co/how-does-a-hacker-hack-a-phone-how-to-avoid-phone-hacking/ https://www.hackerslist.co/how-does-a-hacker-hack-a-phone-ho...
- ewg4345h43 5y agoAMD 5850U beats Apple M1 in multicore performance by 29% having the same power consumption (15 Watt): https://www.cpubenchmark.net/compare/AMD-Ryzen-7-PRO-5850U-vs-Apple-M1-8-Core-3200-MHz/4198vs4104 https://www.cpubenchmark.net/compare/AMD-Ryzen-7-PRO-5850U-v... but is 19% slower in single core performance. However, if you consider that AMD uses 7nm and Apple 5nm technology to build their processors, AMD is a lot better.
- andreasley 5y ago"The TDP of the [AMD 5850U] APU is specified at 15 Watt (default) and can be configured from 10 to 25 Watt by the laptop vendor (most chips are configured higher than 15 Watt)." [1] I'd love to see actual measurements for both chips. [1] https://www.notebookcheck.net/AMD-Ryzen-7-PRO-5850U-Processor-Benchmarks-and-Specs.527809.0.html https://www.notebookcheck.net/AMD-Ryzen-7-PRO-5850U-Processo...
- cwizou 5y agoYep, you can see the distribution of results (there aren't a lot) here and it's all over the place for the Ryzen vs M1 : Ryzen : https://www.cpubenchmark.net/cpu.php?cpu=AMD+Ryzen+7+PRO+5850U&id=4198 https://www.cpubenchmark.net/cpu.php?cpu=AMD+Ryzen+7+PRO+585... M1 : https://www.cpubenchmark.net/cpu.php?cpu=Apple+M1+8+Core+3200+MHz&id=4104 https://www.cpubenchmark.net/cpu.php?cpu=Apple+M1+8+Core+320... TDPs don't mean anything even within a vendor lineup, and doing cross comparison is futile (without properly measuring yourself the power consumption at load, then you can start doing real efficiency comparison or apple to apple).
- hajile 5y agoAlso, Intel and AMD chips are allowed to greatly exceed those TDP numbers with as much as 50-60 watts peak consumption.
- mishafb 5y agoThese days nanometers are just marketing, they are disconnected from the actual chip density
- saagarjha 5y agoA couple of people seem surprised that the "idiomatic" Swift code seems to perform much worse. Unfortunately the blog post doesn't provide much details on the code it is actually running, so I tried my hand at guessing: let vC = [Float](repeating: 1, count: 4) func unidiomatic() -> Float { var vA = [Float](repeating: 0, count: 4) let vB = [1, 2, 3, 4] as [Float] var tempA: Float = 0.0 for _ in 0..<1000 { for i in 0...3 { tempA += vA[i] * vB[i] } for i in 0...3 { vA[i] = vA[i] + vC[i] } } return tempA } func idiomatic() -> Float { var vA = [Float](repeating: 0, count: 4) let vB = [1, 2, 3, 4] as [Float] var tempA: Float = 0.0 for _ in 0..<1000 { tempA = zip(vA, vB).map(*).reduce(0, +) for (index, value) in vA.enumerated() { vA[index] = value + vC[index] } } return tempA } When compiled with optimizations (it's unclear if the author did this?), the "idiomatic" code here is indeed much worse. It's easy to fix the worst of that by working on a lazy sequence, i.e. tempA = zip(vA, vB).lazy.map(*).reduce(0, +) which will save on an extra array allocation and instead run the sum "in place" (in this case, vB is recognized as a constant and in both cases and distributed accordingly). Unfortunately there is still a small amount of overhead because zip doesn't know that the arrays are of the same length, so the compiler inserts some extra bounds checks; also, the second loop gets transformed into what is essentially temp = __swift_intrisic_move(vA) for (index, value) in vA.enumerated() { temp[index] = value + vC[index] } vA = __swift_intrisic_move(temp) but this should ideally bring the performance of the two much closer.
- aardvark179 5y agoThanks for that. From the blog post I wasn’t sure how the temp variable was being used and thus how much of the work might be optimised away entirely.
- api 5y agoThat just means the compiler needs more work around generating optimal code. Rust has some similar idioms and does much better, with the difference between "C-like" Rust and idiomatic Rust usually being small to nonexistent. With Rust you can still sometimes hit edge cases though where the compiler spits out slow code for some idiom that should be zero cost.
- asldfjfjqewf 5y agofuck
- Ensorceled 5y ago> where 100% would be the same time as the Firestorm core, and 200% would be twice that time. I wish more articles would explicitly call this out. I've seen 100% used to mean 100% MORE more than a few times ...
- dundarious 5y agoI’m a big fan of 1x, 2x, etc., for this reason. Usually clearly strictly multiplicative, except with annoying constructions like “2x improvement”.
- Ensorceled 5y agoYeah, "2x improvement" or "200% improvement" is always a total crap shoot on what that means.
- mchusma 5y agoI've been very disappointed in my m1 MBA performance. I had used a 8 year old PC desktop and Chromebook before. The PC died, so I tried to get a MBA to replace both, and honestly it's just slower than either at most things. The thing it does well, and the reason I keep using it, is that my Chromebook doesn't support a few software applications I like using. There are also what appear to be intermittent sound card issues. But Everytime I make an appointment to get it fixed, it decides to not have it. I mean it's ok, but I think wait for v2 of the chip. But I just don't get how people's experience with the M1 is so different than mine.
- minhazm 5y agoWhat do you find it to be slow at?
- fiddlerwoaroof 5y agoIt sounds to me like you probably got a bad unit: I did a simple benchmark of compiling the abcl codebase from scratch and the M1 was significantly faster than my year old desktop with an AMD 3800 and 128G RAM. https://twitter.com/fwoaroof/status/1330041394019397636?s=21 https://twitter.com/fwoaroof/status/1330041394019397636?s=21
- turbinerneiter 5y agoAs impressive the M1 is, it leaves a sour taste in my mouth. I have a similar issue with Qualcomms chips, and I guess Tensor will have the same problem: I can't actually use them. The M1 innovation is locked to Apple. If I have a great idea for a new device that would be enabled by the M1 perf/power/spec, I'd have no chance of building it. I hope Google continues what they did with Coral with the Tensor chip. A Raspberry Pi style device, or a compute module of this chip would be a fever dream. The best thing we have right now is the NXP iMX8 when it comes to performance, and still the RPi when it comes to ease of use. Maybe if have to dig into Qualcomm and check how to get hands on their 8xx chips. The fact that there are not really SBCs with them however tells me that it's not easy to get them/use them.
- eternalban 5y agoI submitted this earlier. This github project (not mine) has pretty extensive benchmarks and the M1 makes a very strong showing. https://news.ycombinator.com/item?id=28346908 https://news.ycombinator.com/item?id=28346908 On another note, I was amazed to see the SHA-1 and SHA-256 (and the Blake2b) performance numbers when running the benchmark of minio’s blake2b-simd (over M1 Golang) on a 16GB M1 Air. For some reason, Go on M1’s SHA-1 and SHA-256 are getting orders of magnitude better numbers (~2.5GB/sec!) and even the Blake2b code is beating the numbers for the same code running on an intel Air (which uses the SIMD codepath). https://github.com/minio/blake2b-simd https://github.com/minio/blake2b-simd
- hajile 5y agoAn interesting thought is the comparison to x86. Icestorm cores max out at 2GHz, but have 30-50% the performance of the 3.2GHz Firestorm cores. Accounting for that frequency difference, the actual performance difference if Icestorm were to boost clocks would be closer to 50-60% of the Firestorm IPC. Zen 3 at 4.9GHz trades blows with M1 at 3.2GHz in single-core benchmarks. It seems when you adjust all the things that Icestorm should be 10-30% slower than Zen 3. Putting that in perspective, Icestorm cores (based on this one microbenchmark) would have around the same performance per clock as the original Zen cores, but only consume a 5-10% of the actual power consumption.