<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:#000000">Hi Erik,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:#000000">Thanks for the quick reply! It certainly sounds like Epyc may be an interesting and competitive option. <br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:#000000"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:#000000">Best,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:#000000">Geraint<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 20 Jan 2020 at 18:19, Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu">schnetter@cct.lsu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Geraint<br>
<br>
Regarding BLAS: I recommend using OpenBLAS instead of MKL there (but<br>
haven't compared performance). There is a thorn<br>
ExternalLibraries/OpenBLAS (part of the ET, but not enabled by<br>
default) that interfaces to OpenBLAS and/or builds OpenBLAS if it is<br>
not already available on the system.<br>
<br>
I am not aware of any issues. Regarding benchmarking, thorn<br>
CactusUtils/Vectors supports SIMD vectorization, and it should already<br>
support Epyc. From the technical discussions on the web it seems that<br>
they should be well suited for the ET. In particular the large L1<br>
instruction cache should be quite beneficial.<br>
<br>
Thank you for the pointer to the Prace best Epyc practices.<br>
<br>
-erik<br>
<br>
On Mon, Jan 20, 2020 at 11:50 AM Geraint Pratten<br>
<<a href="mailto:geraint.pratten@gmail.com" target="_blank">geraint.pratten@gmail.com</a>> wrote:<br>
><br>
> Hi everyone,<br>
><br>
> Does anyone have any experience running on AMD Epyc cores? It seems that these are becoming quite trendy and I found a pretty decent best practice guide that Prace released<br>
><br>
> <a href="http://www.prace-ri.eu/best-practice-guide-amd-epyc" rel="noreferrer" target="_blank">http://www.prace-ri.eu/best-practice-guide-amd-epyc</a><br>
><br>
> However, whenever I've compiled ET recently its typically been on Intel cores + Intel compiler + Intel MKL etc. However, Intel MKL is notorious for being subotpimal on non-Intel cores. Does anyone know of any possible issues that could arise when running ET on AMD Epyc cores? Similarly (and likely optimistically), has anyone had the chance to benchmark the performance of ET on the AMD cores?<br>
><br>
> Thanks!<br>
> Geraint<br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@einsteintoolkit.org" target="_blank">Users@einsteintoolkit.org</a><br>
> <a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.einsteintoolkit.org/mailman/listinfo/users</a><br>
<br>
<br>
<br>
-- <br>
Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>><br>
<a href="http://www.perimeterinstitute.ca/personal/eschnetter/" rel="noreferrer" target="_blank">http://www.perimeterinstitute.ca/personal/eschnetter/</a><br>
</blockquote></div>