<div dir="ltr">+1 for Threadripper or Ryzen Pro</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 3, 2018 at 7:48 PM, Grzegorz Junka <span dir="ltr"><<a href="mailto:list1@gjunka.com" target="_blank">list1@gjunka.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
On 03/01/2018 08:21, Iblis Lin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
forgot to CC the list.<br>
<br>
<br>
On 01/03/2018 01:21 PM, Iblis Lin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
well, purchasing decision is up to you, but I want to share my personal<br>
experience:<br>
<br>
I will vote -100 for the Ryzen build. For me, the term "Ryzen" means<br>
malicious trolling.<br>
<br>
It wasted my time and mental efforts.<br>
<br>
I will show you my journal:<br>
<br>
- I set up the Ryzen box in 2017/5. Mine is 1700 (8 cores 16 threads).<br>
<br>
- I install Arch Linux, ran CouchDB on it... and found the machine<br>
crash and reboot regularly in an interval of 2-3 days.<br>
<br>
- I also tried to build mainline kernel, (at that moment, it's 4.12<br>
IIRC), not work , still crashing or freezing.<br>
<br>
- Another test: disabling all deamon, the box can be alive over a week.<br>
<br>
- Changing memory module in 2017/6, not work.<br>
<br>
- 2017/9 I RMA-ed it.<br>
<br>
- After RMA, it still keeps crashing, hard freezing, soft freezing...<br>
within 3-6 hr if I run something on it.<br>
<br>
the kill-ryzen script DOES kill my box, even it's the new CPU back<br>
from RMA.<br>
<br>
The *improvement* is the crashing interval shrunk. Thank you AMD.<br>
<br>
- 2017/10, I changed my OS from Arch to Ubuntu. not work.<br>
<br>
<br>
On 01/03/2018 06:46 AM, Adam Rutkowski wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey all,<br>
<br>
I'm thinking of building a Ryzen machine, mainly for Erlang development. There's this rather obscure bug with some Ryzen processors on Linux/BSD [1] and I'm worried I might be getting a unit from the faulty batch; I have no means of verifying this before purchasing from my local suppliers. I'm wondering if I should I expect any issues with Erlang VM doing the multi-core heavy lifting.<br>
<br>
Cheers<br>
<br>
[1]: <a href="https://www.phoronix.com/scan.php?page=news_item&px=Ryzen-Segv-Response" rel="noreferrer" target="_blank">https://www.phoronix.com/scan.<wbr>php?page=news_item&px=Ryzen-Se<wbr>gv-Response</a><br>
<br>
<br>
</blockquote></blockquote></blockquote>
<br></div></div>
Interestingly, it's not that not choosing Ryzen guarantees you a worry-free reality:<br>
<br>
<a href="http://www.dailymail.co.uk/sciencetech/article-5232037/Security-flaw-Intel-chips-past-decade.html" rel="noreferrer" target="_blank">http://www.dailymail.co.uk/sci<wbr>encetech/article-5232037/Secur<wbr>ity-flaw-Intel-chips-past-<wbr>decade.html</a><br>
<br>
Arguably 50% slowdown or a security flaw is better than a random crash. But maybe the real lesson is to choose a processor that doesn't have any known vulnerability so far, e.g. Threadripper or a dedicated server processor?<br>
<br>
GrzegorzJ<div class="HOEnZb"><div class="h5"><br>
______________________________<wbr>_________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/list<wbr>info/erlang-questions</a><br>
</div></div></blockquote></div><br></div>