richierich1212
Platinum Member
- Jul 5, 2002
- 2,741
- 360
- 126
Bulldozer@2GHz? OMG AMD is doomed!
No, Faildozer version 2.0.
Trolling is not allowed
Markfw
Anandtech Moderator
Last edited by a moderator:
Bulldozer@2GHz? OMG AMD is doomed!
I have invited him here, but he has not as of yet, accepted the invite.Don't Jinx us, please!!!!
Y is he not here, he is usually everywhere.
How about Feb 29th?
I kid, I kid...
It's not one day.. it's 3 years. Boom Tiger Lake!
He is a legend in his own mind.
My question was more of a joke because I know people can't break NDAs.
My fear is that they're all fake and ryzen totally sucks on launch day
I have invited him here, but he has not as of yet, accepted the invite.
I knew what you actually meant.No, Faildozer version 2.0.
At least for the 6800K used at Videocardz, it is 3200 16-18-18:Do we know what ram the Intel 8c was using.
Ryzen was using 2400. 17 17 17 I think.
We can normalize it using all these data and remove latancy effects.
This needs to be checked. But it could be exactly that what's causing the mem latency dependency, as optimizing away the slow operations would shift the bottleneck somewhere else.IIRC Atkin sieve modulo operations are all by constants and so should be optimized away to faster operations by any decent compiler.
i know we donot trust WCC, but they are claiming that 28th Feb is the release date? "With shipments expected to commence on the 28th"
i though 28th was the NDA lift date.
I'm visiting US between 18th Feb and 5th March. I just hope there will be enough reviews to show its worth making the purchase from there. Prices in UK are quite a bit inflated by tax. Then buy a motherboard at a later date once all the boards have been tested
So all the leaks are all total BS.... The final samples haven't even gone out yet or not till later tonight!!
That is an odd choice. The game is way too old at this point and I do not think that scene is taxing enough. Besides which how do you control NPCs randomly teleporting in and out?I still say that Oblivion's Imperial Market District (raining weather @ noon) is the best way to check single thread performance.
A better choice would be Counter Strike: Global Offensive with ultra-low config and a custom match with a set number of bots.That is an odd choice. The game is way too old at this point and I do not think that scene is taxing enough. Besides which how do you control NPCs randomly teleporting in and out?
At least for the 6800K used at Videocardz, it is 3200 16-18-18:
https://cdn.videocardz.com/1/2017/0...manceTest-9.0-Evaluation-Version-1000x866.png
This needs to be checked. But it could be exactly that what's causing the mem latency dependency, as optimizing away the slow operations would shift the bottleneck somewhere else.
The RAM used in Ryzen tests was ECC, on AM4 platform. All 2400 MHz RAM has CL17 timings. I have not spotted anything like this in "normal" RAM.Do we know what ram the Intel 8c was using.
Ryzen was using 2400. 17 17 17 I think.
We can normalize it using all these data and remove latancy effects.
That is just false.RAM speed does not matter anymore. The performance difference between 2400 and 3200 is like 1 fps.
The algorithm is not very difficult to follow: https://en.wikipedia.org/wiki/Sieve_of_Atkin The only mod operations are by 60 and these can be replaced by some mul and other non-div ALU ops (look "division by constant" with Google).This needs to be checked. But it could be exactly that what's causing the mem latency dependency, as optimizing away the slow operations would shift the bottleneck somewhere else.
Just guessing (watching taskmgr) they run it on all threads in parallel so on an 8T processor its really a 32mb benchmark, that would make both cache latency and memory latency important.The algorithm is not very difficult to follow: https://en.wikipedia.org/wiki/Sieve_of_Atkin The only mod operations are by 60 and these can be replaced by some mul and other non-div ALU ops (look "division by constant" with Google).
If they are segmenting the sieve then some non-constant mod will appear but they should be negligible. And anyway if their limit indeed is 32 million, the sieve doesn't have to be segmented (unless they did heavy tuning of the algo to play with L1 cache). Next thing to note is that they say the test uses 4MB of memory, so definitely main memory should not have a big impact. OTOH cache latency might have some effect.
Anyway it's hard to say what exactly their benchmark does without reverse engineering it or try to run it with external profiling tools (such as Vtune).
The difference in Prime numbers will be in the realm of 10-15%, based on my own tests.Someone that has a 6800K and RAMs that reach at least 3200 16-18-18 could do the tests both with 3200 16/18 ram and 2400 17-17 ram...
Not to forget: 16T means 64GB then! And this would cause writes too. The question is: Is there some sharing of data? Of course, this only applies, if they don't work on these 4MB with all threads.Just guessing (watching taskmgr) they run it on all threads in parallel so on an 8T processor its really a 32mb benchmark, that would make both cache latency and memory latency important.
absolutely. my 300-500 fps drops massively from about the 8th bot, even though I have a 4790K @ 4.8 (and a gtx 1070 alleviates every concern about GPU bound problems).A better choice would be Counter Strike: Global Offensive with ultra-low config and a custom match with a set number of bots.
8 bots 8 threads...absolutely. my 300-500 fps drops massively from about the 8th bot, even though I have a 4790K @ 4.8 (and a gtx 1070 alleviates every concern about GPU bound problems).
Being a 4T machine having 2 fast DIMMs the analysis might become skewed a bit. I'll include your numbers, too. Maybe cache thrashing causes a perf stall/drop (per core) on SMT machines.The difference in Prime numbers will be in the realm of 10-15%, based on my own tests.
Core i5 6600k @ 4Ghz:
2133 CL 15 - Prime scores 34-36
3000 CL 15 - Prime scores 38-41
I wonder what todays ryzen leaks will be
The algorithm is not very difficult to follow: https://en.wikipedia.org/wiki/Sieve_of_Atkin The only mod operations are by 60 and these can be replaced by some mul and other non-div ALU ops (look "division by constant" with Google).
If they are segmenting the sieve then some non-constant mod will appear but they should be negligible. And anyway if their limit indeed is 32 million, the sieve doesn't have to be segmented (unless they did heavy tuning of the algo to play with L1 cache). Next thing to note is that they say the test uses 4MB of memory, so definitely main memory should not have a big impact. OTOH cache latency might have some effect.
Anyway it's hard to say what exactly their benchmark does without reverse engineering it or try to run it with external profiling tools (such as Vtune).