BallaTheFeared
Diamond Member
- Nov 15, 2010
- 8,115
- 0
- 71
Not to mention there are no Vishera products on that review like FX8350, FX6300 etc


Not to mention there are no Vishera products on that review like FX8350, FX6300 etc
My thoughts exactly, after benching my HD4600 in Dota 2 I know for a fact Ra was at best laning and none of his 3 minute strip is with a late game 5v5 team fight.
No question about it, Intel is better in gaming but the FX 6350 is a better all around cpu than i3 3225, it even matches the intel chip in gaming. If you calculate the averages, both high and minimums across all games they're evenly matched. $140 and below there's real competition guys, make no mistake about it. For anything higher than $140, Intel just trashes AMD, no doubt.
What baffles me is the constant AMD bash feast even when they offer a compelling alternative such as the FX 6350, a cpu that is priced the same as the Intel, performs similarly in games and better in most of the applications out there.
So to sum up, FX6300 OCed to 4GHz is within 10-15% of the Core i5 3570K at HALF the COST. You can even buy a $30 heat-sink and OC to 4.6GHz and have almost the same performance at again a lower price.
That $100 price difference can get you an HD7950 over HD7790. No matter how fast the Core i5 is, any gamer will be way better with FX6300 + HD7950 than core i5 + HD7790.
That's the nice thing about GPUs, you can turn down settings and reduce their load a hundred fold, there is no setting that does the same for cpu requirements.
Apples > Oranges
Big deal here. Really.
So you are arguing that turning down the settings have no effect on minimum FPS?
An overclocked 6300 still won't beat a stock i3 in many cpu limited titles.
Which is where I see the 6300 vs i3 debate, on one side you can see when a game can use more threads the 6300 makes a compelling choice, then all of a sudden the i3 guy posts the cpu limited games and the 6300 looks bad. I try to stay out of these discussions, because of the price point and the needs of others and yada yada blah blah, but my personal feeling is to save and get the best overall gaming processor for another few hours of work at min wage.
Here is my issue with both.
Say you budget $130 for the cpu, $200 for the gpu.
That's the nice thing about GPUs, you can turn down settings and reduce their load a hundred fold, there is no setting that does the same for cpu requirements.
Apples > Oranges
Not to mention there are no Vishera products on that review like FX8350, FX6300 etc
Also a 6300 wouldn't touch an overclocked i5 in gaming, not even close. An overclocked 6300 still won't beat a stock i3 in many cpu limited titles.
CPU limited titles? A lot of you guys need to understand "cpu limited" and learn how to clarify and into Poorly CPU threaded, and well CPU threaded titles. Furthermore, everyone claiming "cpu limited" should always clarify the type of game we are talking about, older and unoptimized for more threads, or newer and optimized for more threads. Tom's review itselfs proves my point, the Propus Athlon II X4 640 was slower in many newer titles that are considered "gpu limited". Why? Aren't those games "gpu limited"?
Same for those pushing for Pentiums G1220, and thinking it will play crysis 3. The game is so called "gpu limited", but then, if so, why isn't the G1220 scoring as the i5s in the game, if it is not "cpu limited"?
All games, one way or another, are CPU limited, the difference is how well they can use the CPU threads available. Some are more graphically intensive than others, highlighting the lack of GPU power more abruptly, hence why many people so call them "gpu limited". But again, if crysis 3 is not "CPU limited", why isn't the "mighty" G1220 scoring as the i5?
Let's break the broad "cpu limit" concept games into "poorly threaded" and "well threaded". So what you meant was that an i3 will be faster than a FX6300 in poorly threaded games?
Yeah, because it's really tough to add 10% onto the 8150 score![]()
10% is 74% of Vishera improvement over bulldozer at equal frequency
for games tested by hardware.fr on average.
http://www.hardware.fr/articles/880-6/bulldozer-vs-piledriver-4-ghz.html
One must live with the games as they are. If the cpu is the limiting factor, it is by definition, cpu limited. Whether it is poorly threaded or not is irrelevant really. If what you are implying is that poorly threaded games penalize AMD hardware because it has more threads and lower single threaded performance, that may be true, but the performance as they say "is what it is". Calling it "poorly threaded" instead of "cpu limited" does not change anything. If you wish to blame the programmers for AMDs poor performance in certain games, you certainly can do so. One could just as easily blame AMD for designing cpus with low single threaded performance. In the end it doesnt matter, because blaming either or both does not change the performance.
On the contrary, there are plenty of CPU power available that is not being utilized. Hence, the bottleneck exists elsewhere.
Thread limited seems more appropriate. When only 1 or 2 cores/threads are being utilized by a program and you have the capacity for 4/8 cores/thread, that is not a hardware based bottleneck. This is a software induced bottleneck. Call it for what it is. The CPU is not the limiting factor, it is the poor coding that inhibits better performance.
Even a 5GHz 4670K is considered a "bottleneck" by your existing definition when a program only uses 1 or 2 thread and caps CPU usage on the 1 or 2 cores. However, the reality is that the CPU is not being utilized at 100% capacity. Artificial limiters caused by the software does not mean that the the hardware resources have been depleted and a specific piece of hardware has become a "bottleneck". On the contrary, there are plenty of CPU power available that is not being utilized. Hence, the bottleneck exists elsewhere.
Are you suggesting the software is the bottleneck? The program can't be a bottleneck. Its an analogy used for hardware. You've gone pretty far off the path with that one.
The performance "is what it is" no matter what the reason.
A bottleneck limits the throughput of associated resources, the term is not reserved for hardware. Even budget allocation can be considered a bottleneck in a system. Consider that you spend extra on a PSU with a higher capacity but you don't utilize the extra capacity. The extra $$$ spent on the PSU could have been used to improve performance by spending the funds elsewhere such as faster memory or better CPU.
This is true but there is also a built in fallacy with this conclusion. When we fail to acknowledge the root cause of the lack of performance, we continue to place the burdens of better performance on the wrong party. It is true that AMDs single thread performance is poor. It is also true that there are limitations to single core performance. It is further true that multi-core scaling can be improved drastically(more true for AMD). AMD and Intel are able to address single thread performance and multi-core scaling. The performance limitations of a singe core/thread are boundaries that may potentially be extended with new technology but the the current logical steps to circumvent this boundary is to incorporate multiple cores. At this point, any software developer that creates a product that caps out 1 or 2 threads is creating an artificial bottleneck and the blame, thus, should be directed at the poor coding and not the lack of resources. The other caveat is that the enthusiast market is not the primary target for game developers and, therefore ,they will not code for multiple threads until their target audience starts to feel the performance issues. On the other hand, observation of the professional software development show a greater utilization of multiple threads. Newer generation of productivity software has been increasingly coded for multiple threads as competition is present and the consumer will spend their $$$ on the product that can save the most time and $$$.
So for a $330 CPU & GPU budget, lets go a step further and include the motherboard into the mix. Let us just assume $70 for the motherboard to bring the balance to $400 for the three components.
CPU: Intel Core i5-4430 3.0GHz Quad-Core Processor ($174.99 @ Amazon)
Motherboard: MSI B85M-G43 Micro ATX LGA1150 Motherboard ($74.24 @ Amazon)
Video Card: Sapphire Radeon HD 7850 2GB Video Card ($153.98 @ Newegg)
Total: $403.21
CPU: AMD FX-6300 3.5GHz 6-Core Processor ($117.98 @ Outlet PC)
Motherboard: Biostar TA970 ATX AM3+ Motherboard ($69.99 @ Newegg)
Video Card: Sapphire Radeon HD 7950 3GB Video Card ($199.99 @ Newegg)
Total: $387.96
CPU: Intel Core i3-3220 3.3GHz Dual-Core Processor ($118.99 @ Amazon)
Motherboard: Gigabyte GA-B75M-HD3 Micro ATX LGA1155 Motherboard ($64.99 @ Microcenter)
Video Card: Sapphire Radeon HD 7950 3GB Video Card ($199.99 @ Newegg)
Total: $383.97
Each of these 3 builds would have their benefits and weaknesses. One could argue that a particular bundle may be superior at a particular task but arguing that any one of these three are hands down superior to the other two would be a fallacy. Systems are built based on the need of the user. The argument for the general performance of a single component is typically moot in a system build that has a budget and goal in mind.
This is true but there is also a built in fallacy with this conclusion. When we fail to acknowledge the root cause of the lack of performance, we continue to place the burdens of better performance on the wrong party. It is true that AMDs single thread performance is poor. It is also true that there are limitations to single core performance. It is further true that multi-core scaling can be improved drastically(more true for AMD). AMD and Intel are able to address single thread performance and multi-core scaling. The performance limitations of a singe core/thread are boundaries that may potentially be extended with new technology but the the current logical steps to circumvent this boundary is to incorporate multiple cores. At this point, any software developer that creates a product that caps out 1 or 2 threads is creating an artificial bottleneck and the blame, thus, should be directed at the poor coding and not the lack of resources. The other caveat is that the enthusiast market is not the primary target for game developers and, therefore ,they will not code for multiple threads until their target audience starts to feel the performance issues. On the other hand, observation of the professional software development show a greater utilization of multiple threads. Newer generation of productivity software has been increasingly coded for multiple threads as competition is present and the consumer will spend their $$$ on the product that can save the most time and $$$.