|
A SWEATY FATBEARD posted:Hmmm there seems to be a shortage of fast RAM over here in Croatia; the supply is spotty at best and you have to preorder your sticks if you want anything faster than 2400mhz. I bet this has something to do with Ryzens selling like hotcakes. Hmm, is amazon.de an option?
|
#
?
Aug 5, 2017 02:04
|
|
|
|
| # ? Apr 19, 2024 22:05 |
|
|
Measly Twerp posted:Hmm, is amazon.de an option? Importing hardware on your own is always an option, and I'll probably do just that. Buying a R7 system in the late fall or so, by then the mainboard/RAM compatibility is going to improve a great deal and bugs in BIOSes will be ironed out.
|
|
#
?
Aug 5, 2017 02:09
|
|
GAY 4 ORGANS
|
People were saying that the 1920X didn't have the best pricing, looks like there's gonna be a plain 1920 part that should be more appealing. http://www.pcgamer.com/amds-partners-detail-unannounced-threadripper-1920-cpu-in-support-docs/ quote:AMD has been slow playing the launch of its Threadripper lineup by first announcing the 1950X ($999) and 1920X ($799), then later unveiling the 1900X ($549). Now it appears there is a fourth SKU, one that will not support AMD's extended frequency range (XFR) technology.
|
|
#
?
Aug 5, 2017 02:18
|
|
|
MaxxBot posted:Now it appears there is a fourth SKU, one that will not support AMD's extended frequency range (XFR) technology Which means its cheaper and better right?
|
|
#
?
Aug 5, 2017 02:53
|
|
|
Palladium posted:Which means its cheaper and better right? Depends actually. There is a rumor going around that the XFR enabled SKUs can hit 4.2Ghz, it's possible there might be legitimate binning differences between X and non-X SKUs for TR4.
|
|
#
?
Aug 5, 2017 03:48
|
|
|
The 1920 also has a lower TDP but I'm not sure if it's binned for lower TDP like the 1700 or just has a lower listed TDP due to the lack of XFR.
|
|
#
?
Aug 5, 2017 04:00
|
|
|
e: wrong thread
eames fucked around with this message at 10:29 on Aug 5, 2017 |
|
#
?
Aug 5, 2017 10:22
|
|
|
eames posted:I suspect Threadripper (B1 "stepping") will suffer from the same problem and Epyc will have the fix (B2 stepping) Someone on Reddit claims his Epyc server is segfaulting on the Phoronix stress test 
|
|
#
?
Aug 5, 2017 14:15
|
|
|
God dammit, why must the available CPU options be like this.
|
|
#
?
Aug 5, 2017 14:18
|
|
|
Mr.Radar posted:Phoronix has released a test suite that can reliably reproduce the Ryzen GCC crash bug within minutes both on stock configurations and with both SMT turned off and the memory down-clocked to 2133 MHz. Unfortunately AMD isn't giving them Threadripper or Epyc samples so there's no word yet if they also suffer from this bug. I fear this might prove to be rather costly issue for AMD.
|
|
#
?
Aug 5, 2017 14:45
|
|
|
AMD CPU discussion: gently caress, maybe version 2 will be better
|
|
#
?
Aug 5, 2017 14:46
|
|
|
AMD CPU discussion: 64C/128T
|
|
#
?
Aug 5, 2017 14:51
|
|
|
where is the fault, amd or people not updating their software in the past 8 years because amd hasn't had a good cpu since then?
|
|
#
?
Aug 5, 2017 14:54
|
|
|
AMD CPU discussion: Trying to B1 step ahead of Intel.
|
|
#
?
Aug 5, 2017 15:00
|
|
|
Will be interesting to see how well the new 6core intels work. That gamernexus 1700x vs 7700k review was quite bleak, ryzen still leaves a ton of gpu performance unused.
|
|
#
?
Aug 5, 2017 16:48
|
|
|
Ihmemies posted:Will be interesting to see how well the new 6core intels work. That gamernexus 1700x vs 7700k review was quite bleak, ryzen still leaves a ton of gpu performance unused. Weird, I got the opposite impression
|
|
#
?
Aug 5, 2017 16:49
|
|
|
Ihmemies posted:Will be interesting to see how well the new 6core intels work. That gamernexus 1700x vs 7700k review was quite bleak, ryzen still leaves a ton of gpu performance unused. non-x, and how much ram OC did he do?
|
|
#
?
Aug 5, 2017 17:08
|
|
|
Phoronix posted part 2 of their segfault investigation: http://www.phoronix.com/scan.php?page=article&item=ryzen-segv-continues&num=1Phoronix posted:So that's where I am at now. Yesterday's testing showed the problem can be reproduced even if SMT is disabled and even if forcing the memory to DDR4-2133. This latest testing shows the problem isn't isolated to GCC that it can also happen with LLVM Clang (in fact, worse) as well as when using the latest GCC 8 development code. Disabling ASLR did not help the situation and running the other stressing concurrent workloads for server/multimedia/scientific didn't yield any segmentation faults in an hour unlike the compilation workloads yielding 50+ per hour. Clearing the BIOS and leaving the defaults also hasn't yielded any change. Some have also said they have been able to reproduce this problem on Epyc CPUs, but unfortunately it doesn't look like we will be receiving any Threadripper / Epyc review samples.
|
|
#
?
Aug 5, 2017 18:10
|
|
|
It's stunningly specific. They should really take the microcode that checks if it's running a C compiler and creates random errors out, I don't think that's going to be their silver bullet versus Intel. Wait, gently caress. The conspiracy theorist in me almost imagines some sort of insane "Reflections on Trusting Trust" scheme that's not quite working right.
|
|
#
?
Aug 5, 2017 18:21
|
|
|
From the linustechtips video going live in a few hours:     
|
|
#
?
Aug 5, 2017 18:28
|
|
|
Shame the Ryzen system is hobbled with slow RAM... AMD really needs to tweak the architecture in this regard.
|
|
#
?
Aug 5, 2017 18:33
|
|
|
Would have been nice to see how the TR system would have acted with DDR4-3200 memory. But I guess they compared the system completely stock to their test bench.
|
|
#
?
Aug 5, 2017 18:36
|
|
|
HalloKitty posted:Shame the Ryzen system is hobbled with slow RAM... AMD really needs to tweak the architecture in this regard. There's no reason it can't use DDR4-3200, beyond what Combat Pretzel mentioned about using a stock system for the test bench. I'm actually impressed that it did so well when not using DDR-3200.
|
|
#
?
Aug 5, 2017 18:56
|
|
|
Sinestro posted:It's stunningly specific. They should really take the microcode that checks if it's running a C compiler and creates random errors out, I don't think that's going to be their silver bullet versus Intel. It seems that what Phoronix is experiencing is in fact normal behaviour while compiling PHP: quote:conftest segfaults might be normal, part of autoconf trying ( on purpose ) to find broken configuration options so it knows what to avoid. This would align with my conftest segfaults appearing in my dmesg when test-suite starts a new php run a segault in bash or gcc would be a different story... However, he was able to cause Clang to crash, but it seems that the kill_ryzen.sh script is still the best method for testing. After 1.5 hours I've not been able to reproduce it yet.
|
|
#
?
Aug 5, 2017 19:07
|
|
|
^^^ So premature ejaculation about nothing then? Come to think of it, autoconf does generate those configure.sh scripts, which invoke gcc tons of times compiling and running test files? Kind of make sense some of that output breaks.SourKraut posted:There's no reason it can't use DDR4-3200, beyond what Combat Pretzel mentioned about using a stock system for the test bench. I'm actually impressed that it did so well when not using DDR-3200. Combat Pretzel fucked around with this message at 19:16 on Aug 5, 2017 |
|
#
?
Aug 5, 2017 19:12
|
|
|
Malloc Voidstar posted:From the linustechtips video going live in a few hours: So they're going to run Rise of the Tomb Raider at 4K on a GTX 1080 Ti and call that a test of CPU gaming performance? :iamafag:
|
|
#
?
Aug 5, 2017 19:32
|
|
|
Combat Pretzel posted:^^^ So premature ejaculation about nothing then? Come to think of it, autoconf does generate those configure.sh scripts, which invoke gcc tons of times compiling and running test files? Kind of make sense some of that output breaks. Confirmed, I'm running the stress test on my Xeon E5-2650L VPS and conftest is throwing segfaults just like the Ryzen systems in the article. welp i expected better from phoronix repiv fucked around with this message at 19:43 on Aug 5, 2017 |
|
#
?
Aug 5, 2017 19:33
|
|
|
TheJeffers posted:So they're going to run Rise of the Tomb Raider at 4K on a GTX 1080 Ti and call that a test of CPU gaming performance? :iamafag:
|
|
#
?
Aug 5, 2017 19:43
|
|
|
Malloc Voidstar posted:It at least shows that Threadripper isn't garbage at games Tadaaaaa https://www.youtube.com/watch?v=decz1N9YpOw
|
|
#
?
Aug 5, 2017 20:04
|
|
|
"Threadripper is pretty good but holy poo poo the Area 51 sucks."
|
|
#
?
Aug 5, 2017 20:31
|
|
|
TheJeffers posted:So they're going to run Rise of the Tomb Raider at 4K on a GTX 1080 Ti and call that a test of CPU gaming performance? :iamafag: Realistically, i think the vast vast majority of people who buy these things for gaming will be using 4k. It's the real world test I guess,with 1080p essentially being a non-real world theoretical test.
|
|
#
?
Aug 5, 2017 21:16
|
|
|
Cygni posted:Realistically, i think the vast vast majority of people who buy these things for gaming will be using 4k. It's the real world test I guess,with 1080p essentially being a non-real world theoretical test. If you're going to take a game that's not generally CPU-bound to begin with and play it at a resolution where it will assuredly be GPU-bound, you're essentially telling your audience that it's basically pointless to buy a $500+ CPU for high-resolution gaming, which is true—the GTX 1080 Ti is the far more important determinant there. It's also the best case for AMD because it basically tells you nothing about how the unique packaging decisions of Threadripper affect gaming performance. That same graphics card can still bind up certain games on a single thread/core even at 2560x1440 for high-refresh-rate gaming, and I'd bet there's an equally large or larger contingent of loaded gamers with high-refresh 2560x1440 displays who are curious how the chip performs under those circumstances. In that case, you are at least doing something that's both representative and CPU-bound. All I'm getting at is that if you're going to present a GPU-bound test as a CPU benchmark, you should at least be clear about that with your audience. It tells you basically nothing about CPU performance, and that seems kind of silly (at best) or disingenuous (at worst) for something that's ostensibly a CPU review.
|
|
#
?
Aug 5, 2017 21:46
|
|
|
https://www.phoronix.com/forums/for...7437#post967437quote:I am running the test in a Core i5 laptop and the conftest segfault appear here too. Michael, did you get only conftest segfaults? 
|
|
#
?
Aug 5, 2017 22:06
|
|
|
Never trust someone whose forum URL reads https://www.phoronix.com/forums/forum/phoronix.
|
|
#
?
Aug 5, 2017 22:41
|
|
|
Sudden plot twist, the empire strikes back. Err wait I don't think that metaphor works. gently caress star wars.
|
|
#
?
Aug 5, 2017 23:22
|
|
|
Yeah, the Phoronix article was junk and they've retracted it for now. Phoronix posted:As a result of feedback, currently working on some updated results. As some have pointed out, the conftest segmentation faults aren't specific to Ryzen, so updating the tests to avoid confusion. Though one area being explored now as well is the Clang segmentation faults shown in the original article, not originating from conftest as well as Clang being able to yield the system hanging hard where the system is unresponsive and SSH is not working. Plus also incorporating more Ryzen-Kill tests as outlined in the aforelinked article. As many readers have pointed out, BSD developers have also discovered a Ryzen bug. More details soon.
|
|
#
?
Aug 6, 2017 00:34
|
|
|
Bizarre that he's never across this issue given he's spent a lot of time benchmarking Intel CPUs in the past.
|
|
#
?
Aug 6, 2017 00:37
|
|
|
Too bad, since if that issue would have been real, it'd have kept me financially responsible. 
|
|
#
?
Aug 6, 2017 01:10
|
|
|
Combat Pretzel posted:Too bad, since if that issue would have been real, it'd have kept me financially responsible. Getting THREADRIPPER?
|
|
#
?
Aug 6, 2017 01:51
|
|
|
|
| # ? Apr 19, 2024 22:05 |
|
|
So I'm reading some blurb that the Alienware box(es) that went around for testing might have had a preproduction CPU, and the retail CPUs have slightly better performance. Hothardware ran a review with a 2900 Cinebench score, and was then contacted by AMD, who noted that it might be a preproduction CPU and sent them a new one, which resulted in a score of 3000 and some pocket change. I've noted Linus' Cinebench score also is roughly 2900, so it might be another preproduction CPU, if that poo poo is real. So the current numbers still aren't final. https://hothardware.com/news/ryzen-threadripper-alienware-area-51-transplant I mean, Cinebench, yea. But it's indicative that other metrics might have changed, too. GRINDCORE MEGGIDO posted:Getting THREADRIPPER?
|
|
#
?
Aug 6, 2017 02:37
|
|