Bug 1619062 - scamp: use openblas instead of atlas
Summary: scamp: use openblas instead of atlas
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: scamp
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christian Dersch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-20 00:32 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2020-04-08 02:53 UTC (History)
1 user (show)

Fixed In Version: scamp-2.7.8-1.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-08 02:53:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dominik 'Rathann' Mierzejewski 2018-08-20 00:32:57 UTC
Description of problem:
Please BuildRequire: openblas instead of atlas where available (x86_64 %{ix86} armv7hl %{power64} aarch64 s390x, see %{openblas_arches} macro defined in openblas-srpm-macros package). Currently, it's available on all primary Fedora arches, so you can technically skip using the macro.

Version-Release number of selected component (if applicable):
scamp-2.0.4-12.fc29

Additional information:
OpenBLAS selects best code path for the target architecture at runtime unlike ATLAS.

A lot of benchmarks around the net suggest openblas is faster than ATLAS in most workloads:
https://github.com/tmolteno/necpp/issues/18
http://blog.nguyenvq.com/blog/2014/11/10/optimized-r-and-python-standard-blas-vs-atlas-vs-openblas-vs-mkl/
https://freddie.witherden.org/pages/blas-gemm-bench/
http://nghiaho.com/?p=1726

Many Fedora packages have switched to openblas already (e.g. scalapack and all dependent ones and numpy).

Comment 1 Ben Cotton 2019-08-13 17:10:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 2 Ben Cotton 2019-08-13 19:45:39 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 3 Fedora Update System 2020-03-30 15:18:12 UTC
FEDORA-2020-7a86eca506 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-7a86eca506

Comment 4 Fedora Update System 2020-03-31 01:52:24 UTC
FEDORA-2020-7a86eca506 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-7a86eca506`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7a86eca506

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2020-04-08 02:53:24 UTC
FEDORA-2020-7a86eca506 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.