[HEADSUP] Atlas changed libraries

Frantisek Kluknavsky fkluknav at redhat.com
Mon Sep 23 14:21:30 UTC 2013

On 09/22/2013 09:27 PM, Richard W.M. Jones wrote:
> Grrrr.
> Please don't [to ATLAS upstream, not Susi] do this.  It breaks all
> sorts of scenarios, especially virtual machine migration or simply
> moving hard disks from one physical machine to another.
> Arrange your code so it chooses the best available routines when the
> program starts up, and compile every feasible alternative into the
> binary.  Or use kernel vdso/user-helper functions when that is
> applicable.
> Rich.

Atlas aims for a relatively narrow set of use cases. No virtualization. 
No migration. Just the best possible performance on one given machine.
Virtual machines are notoriously known for varying performance. One can 
not tune without exact benchmarking.

More information about the devel mailing list