#10508: Update ATLAS to stable version 3.10.1
-------------------------------------------------------------------------------------------------------------------------+
Reporter: vbraun
| Owner: tbd
Type: enhancement
| Status: closed
Priority: major
| Milestone: sage-5.10
Component: packages: standard
| Resolution: fixed
Keywords: ATLAS spkg
| Work issues:
Report Upstream: Reported upstream. No feedback yet.
| Reviewers: Benjamin Jones,
Karl-Dieter Crisman, Dmitrii Pasechnik, Georg Weber, François Bissey, John
Palmieri, Volker Braun
Authors: Volker Braun, Jeroen Demeyer, Jean-Pierre Flori
| Merged in: sage-5.10.beta5
Dependencies: #13160, #13395, #13392, #13416, #12994, #9906, #12883,
#13123, #13415, #14344, #14465, #12832, #14617 | Stopgaps:
-------------------------------------------------------------------------------------------------------------------------+
Comment (by leif):
Replying to [comment:64 leif]:
> Replying to [comment:63 jdemeyer]:
> > Timing on x86_64 with `SAGE_FAT_BINARY=yes` on sage.math:
> > {{{
> > real 139m50.733s
> > user 134m30.710s
> > sys 7m12.390s
> > Successfully installed atlas-3.8.4.p1
> > }}}
> > {{{
> > real 350m5.662s
> > user 330m23.460s
> > sys 22m1.010s
> > Successfully installed atlas-3.10.0
> > }}}
> > Why does the new ATLAS take so much longer to build than the old one?
>
> I can beat that:
>
> {{{
> Finished installing shared ATLAS library.
>
> real 821m14.881s
> user 739m58.560s
> sys 58m23.440s
> Successfully installed atlas-3.10.0
> }}}
>
> (That's with `sage -f ...` on an otherwise idle machine, an AMD Fusion
E-450 running Ubuntu 10.04.4 LTS x86_64.)
Same machine, 3.10.1.p0, `SAGE_ATLAS_ARCH` not set (this time with GCC
4.8.0, FWIW):
{{{
real 1244m45.739s
user 998m42.830s
sys 92m27.150s
Successfully installed atlas-3.10.1.p0
}}}
So now seems to take even ''longer'' than 3.10.0 did (although the sysload
was occasionally above the number of cores).
> It took far more time than building ''all of Sage'' [in parallel, on
that dual-core CPU], including the old ATLAS spkg. I currently have no
figures for a ''separate'' ATLAS 3.8.4 build, but the timings from
previous parallel Sage builds on that machine vary between
>
> {{{
> real 214m52.096s
> user 175m5.390s
> sys 9m56.210s
> Successfully installed atlas-3.8.4.p1
> }}}
>
> and
>
> {{{
> real 256m32.949s
> user 217m30.760s
> sys 10m31.050s
> Successfully installed atlas-3.8.4.p1
> }}}
>
> (The LAPACK and BLAS spkg build times in these builds are a few minutes
and less than one minute [wall time], respectively.)
>
> I was actually hoping ATLAS 3.9.x / 3.10 meanwhile "knows" these AMD
CPUs and therefore builds at least a bit ''faster''...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10508#comment:512>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
