Language Selection

English French German Italian Portuguese Spanish

Hands On & Initial Benchmarks With An Ampere eMAG 32-Core ARM Server

Filed under
Graphics/Benchmarks

Especially with Qualcomm's Centriq efforts going quiet in recent months, one of the most interesting ARM server efforts at the moment is Ampere Computing -- the company founded by former Intel president Renee James and with several other ex-Intel employees on staff. They started off with the acquired assets from what was AppliedMicro and their X-Gene ARMv8 IP and for the past year have been improving it into their recently announced eMAG processors.

The eMAG processors announced back in September by Ampere are up to 32-core with a 3.3GHz turbo while having a launch price of $850 USD. Their second processor is a 16-core model with 3.3GHz turbo for $550. Both processors support eight DDR4-2667MHz memory channels, SATA 3.0 storage connectivity, 42 PCI Express 3.0 lanes, and these 16nm FinFET processors have a 125 Watt TDP. Lenovo and other ODMs will be manufacturing servers with eMAG processors although the expected pricing information isn't yet announced.

Read more

More in Tux Machines

FreeBSD Quarterly Status Report

We also provide some up to date information about the status of our IRC channels Read more Also: FreeBSD In Q2'2019 Saw Updated Graphics Drivers, Continued Linux Compatibility Layer

DragonFlyBSD Pulls In AMD Radeon Graphics Code From Linux The 4.7 Kernel

It was just last month that DragonFlyBSD pulled in Radeon's Linux 4.4 kernel driver code as an upgrade from the Linux 3.19 era code they had been using for their open-source AMD graphics support. This week that's now up to a Linux 4.7 era port. François Tigeot who continues doing amazing work on pulling in updates to DragonFlyBSD's graphics driver now upgraded the Radeon DRM code to match that of what is found in the upstream Linux 4.7.10 kernel. Read more

Android Leftovers

TenFourFox FPR16b1 available

FPR16 got delayed because I really tried very hard to make some progress on our two biggest JavaScript deficiencies, the infamous issues 521 (async and await) and 533 (this is undefined). Unfortunately, not only did I make little progress on either, but the speculative fix I tried for issue 533 turned out to be the patch that unsettled the optimized build and had to be backed out. There is some partial work on issue 521, though, including a fully working parser patch. The problem is plumbing this into the browser runtime which is ripe for all kinds of regressions and is not currently implemented (instead, for compatibility, async functions get turned into a bytecode of null throw null return, essentially making any call to an async function throw an exception because it wouldn't have worked in the first place). This wouldn't seem very useful except that effectively what the whole shebang does is convert a compile-time error into a runtime warning, such that other functions that previously might not have been able to load because of the error can now be parsed and hopefully run. With luck this should improve the functionality of sites using these functions even if everything still doesn't fully work, as a down payment hopefully on a future implementation. It may not be technically possible but it's a start. Read more