AMD strong comeback

In the article from the next platform “AMD is finally trusted in the Datacentre again

AMD turned in the best quarter that we can remember, and is now firmly in place as the gadfly counterbalance to the former hegemony of Intel. And that is good for everyone who buys a game console, a PC, an edge device, and a server. And the game is only going to get more interesting with Intel getting its chip together and preparing for a long battle with AMD and other XPU usurpers in chip design and as well as Taiwan Semiconductor Manufacturing Corp in chip etching and packaging.

We do get some hints, however. Lisa Su, AMD’s president and chief executive officer, said that AMD’s datacenter business – at this point meaning Epyc CPUs and Instinct GPU accelerators – comprised more than 20 percent of the company’s overall sales, and the big driver in this quarter was not just second generation “Rome” Epyc 7002 and third generation “Milan” Epyc 7003 server chips – Rome is still outselling Milan, but the crossover is coming in the third quarter of this year – but the Radeon Instinct M100 GPU accelerators launched last fall. The datacenter GPU business more than doubled from a year ago, according to Su, and AMD expects it to continue to grow in the second half of the year as the 1.5 exaflops “Frontier” supercomputer at Oak Ridge National Laboratory in the United States, the as-yet-unnamed pre-exascale system at Pawsey Supercomputing Center in Australia, and the Lumi pre-exascale system in Finland all get their Radeon Instinct motors installed.

the Next Platform “AMD is finally trusted in the Datacentre again”

rsync and write failed with No Space left on Device (28)

If you run an rsync such as this command

% rsync -lH -rva --no-inc-recursive --progress gromacs remote_server:/usr/local

and you encountered something like this

% rsync: write failed on "/usr/local": No space left on device (28)

After checking that the source and destination have sufficient space, you are still encountering the issue, you may want to put this parameter in “–inplace”. According to the rsync man page. “This option changes how rsync transfers a file when its data needs to be updated: instead of the default method of creating a new copy of the file and moving it into place when it is complete, rsync instead writes the updated data directly to the destination file.

WARNING: you should not use this option to update files that are being accessed by others, so be careful when choosing to use this for a copy. For more information, do take a look at

% rsync -lH -rva --inplace --no-inc-recursive --progress gromacs remote_server:/usr/local