3 ms·
> The primary reason someone would buy this thing is for automotive development. Since most cars and infotainment systems run on Arm chips, building software wi
by Aurornis 2y ago
> The primary reason someone would buy this thing is for automotive development. Since most cars and infotainment systems run on Arm chips, building software with an Arm workstation makes sense—it's a lot faster compiling Arm software native on a monster Arm CPU than even the fastest AMD or Intel CPU with emulation.
I think this is a misunderstanding on Jeff's part, or maybe he was given some bad marketing material.
Emulating ARM software is slow, but cross-compiling for ARM is not. Cross-compilers do not rely on emulation to compile.
The reason this machine compiles quickly is that it has 128 cores and a high TDP.
> Note that you can buy every part of this system—aside from System76's case and support—from a retailer like NewEgg (e.g. the motherboard + CPU combo for $2349) should you wish to build a custom arm64 workstation PC.
This link is to a different CPU that is not quite as fast as the one he tested (though still fast) and only has 10Gbe, not 25Gbe. Still a good bargain, but not the same part used in the system.
- bryanlarsen 2y agoCross-compiling can be a pain to set up, though. Sometimes it's easy, sometimes it isn't. I've definitely compiled under emulators in the past just to not have to deal with cross-compilers. I definitely wouldn't spend $7000 to avoid the pain though!
- taeric 2y agoIsn't it typically a flag, nowadays? Even for python, getting an install that works on ARM from X86 is largely `pip install --platform manylinux2014_aarch64 --only-binary=:all:`, if I have it right. I confess it took me longer to find that flag than I'd care to admit. But AWS Lambda using ARM made this something worth finding. And many of the alternatives on how to get the artifacts to deploy did focus on containers for emulation, if I'm remembering correctly.
- jitl 2y agoPython is doing a lot of abstracting for you. In the realm of building C/C++ software using an odd menagerie of system packages and from-source dependencies one might need to figure out the cross-build process of each dependency, and make a prefix for the cross-arch system libraries… it’s doable but the paved path is definitely narrow and there’s lots of thorns when you stray into the jungle. And then you still need to run the tests.
- taeric 2y agoApologies, my point was that for a while, getting python to go cross platform was surprisingly difficult. Specifically if you had any native included, of course. And agreed that you needed a cross compiler with all of the necessary libraries. For common targets, I don't remember this ever being that particularly difficult with gcc?
- bluGill 2y agoIn theory it is a flag. However in practice it almost never works. I cross compile all the time and there is nearly always something that the developers didn't think of (probably didn't know about) that makes their code not cross compile. Automake never works right. Even Cargo often fails to get something right (and I don't know rust/cargo well enough to know how to figure out what, much less how to fix it though I suspect Cargo would fix my bug reports if I could figure out what is wrong with enough detail that they can figure out the issue). Cmake always works in my experience. Note that I didn't mention python above. If python is acceptable performance you probably have enough power (including memory) on the target to just compile everything on that system thus avoiding cross compiling.
- taeric 2y agoFair that there are often problems. My expectations would be that nothing is flawless, with how often native builds can be difficult. Still, I thought for the common targets with minimal dependencies, it was largely a flag. And apologies for the confusion of mentioning python. I did that largely because it was frustratingly hard to get a cross target python for a long time.
- deleted 2y ago[deleted]
- stefan_ 2y agoYeah, I'm not entirely sure who this system is for. A lot of automotive infotainment is AMD now (if you are gonna sell to console makers..) and ARM64 is a perfectly "sane" architecture that has very decent software support in everything you would need to make a cross-compiling toolchain. Ironically the kind of systems that don't have the latter generally can't be very well emulated (or bought as a workstation) either. The last time I wished for a native high performance ARM64 system was using PyInstaller to deploy something not very important to an ARM64 based embedded system which needs the native environment. But that's the reason it was "not very important"; I won't live to see them make a sane Python deployment story.
- geerlingguy 2y ago> I think this is a misunderstanding on Jeff's part, or maybe he was given some bad marketing material. It was more the former, though mostly miswritten... what was in my head and what I wrote at 11pm last night were two different things :) (I've just updated the post) The point is, this machine was built at the request (IIRC) of an automotive manufacturer who was tired of the delay in running a suite of I believe hundreds of ECU tests. So needing to have a machine which could quickly compile the arm64 software, then run it in dozens of VMs to run their test suite. It was expensive in the cloud, and took much longer on a local workstation, so the Thelio Astra was born. Ampere has a synthetic benchmark to kind of illustrate this point (though of course the benchmark is slanted completely in Ampere's favor, as Coremark is one of the few benchmarks where Ampere does better core-for-core than AMD/Intel): https://github.com/AmpereComputing/qemu-coremark?tab=readme-ov-file#example-results https://github.com/AmpereComputing/qemu-coremark?tab=readme-... > This link is to a different CPU that is not quite as fast as the one he tested (though still fast) and only has 10Gbe, not 25Gbe. Still a good bargain, but not the same part used in the system. That's a good point, again I had only checked late last night and thought it was the same M128-30, but alas, it's the 2.6 GHz version. To be honest, I'm not sure how to get the dual 25 GbE version of the board either, maybe ASRock Rack is only selling direct to partners. I will ask about whether it could be put into a bundle on NewEgg, I have no idea how they set up that arrangement, but IMO it should be available! And having the CPU's easily purchasable without a motherboard bundle would be nice, too. They're probably not a high-volume item, but they have their place.
- bluGill 2y agoI don't understand the value? Why not build for your native CPU and run the tests there. Eventually you need to cross compile for the target as well and run integration tests, but the vast majority of your tests should be portable to run on anything you compile for. You probably want to write some custom text fixtures/emulators so that you don't have to test everything in a full car - dangerous error conditions in particular should be tested in emulation as much as possible before you find a lab to run a real world test (if you test them - is it worth exploding an engine just to verify you show the correct RPM?) In the 1980s everything was written in assembly and you depending on the clock speed. However these days embedded should have learned that the CPU you write for will go out of production and so you should write portable code except for the small shim layers that talk to the real hardware.
- cbsmith 2y ago> In the 1980s everything was written in assembly and you depending on the clock speed. However these days embedded should have learned that the CPU you write for will go out of production and so you should write portable code except for the small shim layers that talk to the real hardware. Ah... the illusions of "portability". A lot of the reason you want to test your code is that there may be behaviors specific to the target platform (either in the hardware itself, in the compiler, in the runtime, or in support libraries/frameworks). You may well write with the intent to be portable, but you test for the reality that you never really are.
- bluGill 2y agoTesting on a desktop machine with many cores is not a good simulation of that environment. You run your tests on your local machine as much as possible. Then you run on the real production hardware enough tests to be confident. I don't work automotive, but my application is very similar - an embedded display running ARM CPUs. I do a lot of testing on x86-64 and only rarely encounter portability issues. When I do discover such things they have always been things that I need real hardware to debug on not something an ARM desktop would help with.
- 2y ago