BFG10K
Lifer
- Aug 14, 2000
- 22,709
- 2,980
- 126
Nope, try harder.Originally posted by: MrK6
That's because anything you've stated is a fairy tale.
But none of this changes any of my points.I live in reality, where the easiest ways to overcome an architecture limitation is to go multi-core (every major hardware produce, AMD, intel, and NVIDIA have realized this, for some reason you still can't grasp it). But I guess if we're going to keep dreaming, I'll take a flying car.
I see. You live in ?reality?, but it hasn?t happened yet?That's because no one's coded for it yet,
Because your responses don?t get it.And why do you keep repeating the same stupid arguments every single reply,
This is a strawman argument on your part.If you want to argue the merits of dual-core based on the fact that Solitaire is not coded to support multi-core, my words are lost on such stupidity.
The perfect example of how because you have no answer, you resort to rubbish like this.Perfect example of why I say you've never used a quad-core system. Kind of tough to find merit in something you've never used, I'd imagine.
Thanks for confirming you know nothing about SLI/CF AA modes.Evidently you don't, which, again, is ironically humorous.
Thanks for confirming you know nothing about SLI/CF AA modes.If it's not available in the driver by default, what's the point? Besides, are you really trying to argue a benefit of using more than 16x SSAA? Please.
Actually it has every bearing because it benefits old games, unlike you claims to the contrary.Then say what you mean and not some example that has no bearing to the discussion; learn to formulate an argument.
Right, so why pay more for a quad?But I thought CPUs all flatline in "real" gaming situations, so there's no point?
How exactly have I wasted my money given I have a higher performing part (overall) for less money?Which, again, because architectures show similar limitations, makes no significant difference, so you wasted your money. Thank you again for defeating your own argument.
But I didn?t make the statement, you did. You did it when linking to the 1024x768 benchmarks, and you do it every time you continue to refer to them.And again, your fundamental lack of understanding of gaming performance shows. You constantly make that same statement, but don't even take the time to figure just exactly how wrong you are. Like I said, child covering his ears and yelling.
Let revise my comment - the quad-core is almost never faster than a higher clocked dual core for 3D gaming.So you're wrong 99% then? Let me revise my comment - the quad core is almost always faster than a higher clocked dual core.
Good answer, except it doesn?t address your fundamental flaws in relying on overclocked hardware. So actually it?s quite a worthless response.So you're changing the subject because you agree that I'm right and you have no idea how to retort because of you're fundamental lack of knowledge? Cool.
Again, it?s a simple yes/no question, and yet you still fail to answer it.Kind of funny because I did, but you conveniently ignore every point I nail home and either change the subject or make some restriction that doesn't pertain to the scope of the argument.
I?m not going to close anything because I can?t moderate thread I post in. Sorry to shatter your dreams like that.It's fine, I'm going to see how long this keeps going until you're backed into a corner and either stop replying or (try) to close an "off-topic" thread. Do continue, this is great.
Again you type responses which totally dodge the issue of your defeated arguments in the hopes that somehow people won?t notice.So then you're admitting that you'd like to take up residence at the Dell forum and
have to place discussing taking hardware to the next level in an enthusiast's community. Glad we got that settled.
Because your arguments are wrong.And as I already stated, you lack a fundamental understanding of hardware performance in games, why do you even think you can continue to participate in this discussion?
You do whatever makes you happy, chief.I think the better part is the next time you post and "testing" results, I can just link to this thread to show people to take your findings with a grain of salt. Whatever, it's your hole you're digging.
No it isn?t.Overclocking is guaranteed.
Right, which means even stock + 1 Mhz isn?t guaranteed, according to your own definition. Thanks for agreeing with me.An overclocked speed is not.
There?s no difference except in your semantic and rhetorical games.That's a fundamental difference, one you've missed several times now.
Again overclocking isn?t guaranteed, even by your definition, so I?m not misinterpreting anything.Because you incorrectly interpret results and draw some inane argument that no one else is seeing, doesn't mean my examples aren't robust.
False dilemma logical fallacy on your part. Try option 3: your arguments are wrong.It means you lack the knowledge to follow the logic or ignore the logic because it defeats your argument. Which is it?
Whose statistics? The enthusiast forums which represent a drop in the bucket of all processors sold? Likewise, where are these statistics that show us those two particular processors you linked too overwhelmingly only attain those specific speeds?Except that it follows a general statistic and that a decent overclock is guaranteed for 99%+ CPUs.
No they do not. You use overclocked tests using ?statistics? pulled out from who knows where while completely ignoring the stock guaranteed figures for every such processor ever made. And you wonder why I can?t take your arguments seriously?The examples I make are fine and completely back up my arguments. The extraneous information and tangents you take from them are not.
In any case, the statistics for stock speeds are inherently flawless given a processor that can?t run said speeds is faulty, so my examples are more robust no matter which way you try to spin things.
Again, your arguments completely demonstrate being oblivious to the fact that nobody games at 1024x768, but still attempting to draw inferences into the real world based on unrealistic scenarios.Again, completely demonstrating you lack of knowledge regarding hardware and gaming. That hole's like what, 10 feet down by now?
The key word being if. And that my friend is my entire point; the if doesn?t come up often enough to justify the clock loss and/or higher price from quad-core. It may do in the future, but not now.Nope, the majority of CPU limited situations will show a greater benefit from more cores if supported. Like I said before, you're trading 5% improvement (at the absolute best) for a remarkable 60-80% improvement.
Excellent, so we finally have a have a definite answer. More on this to follow.Because any idiot realizes that most people don't game at 1024x768, I don't.
So again another total dodge of the issue on your part. You?ve admitted that you don?t game at 1024x768 and neither do most people, yet you still attempt to make inferences into the real world from scenarios you yourself agree largely don?t exist.And yet we're getting into double digits the number of times you have faithfully demonstrated your lack of understanding of computer hardware and how it pertains to gaming.
At this point I don?t think anything else needs to be said about that.
Again, if all you?re trying to do is isolate CPU performance then why even bother benchmarking games? 1024x768 gaming results are no more relevant than CPUMark because people don?t run such scenarios in the real world.Those are simple tests to isolate factors of CPU performance in gaming, yet you you can't even understand something so simple.
Here?s a quarter; go and call someone who gives a shit.Like I said, this thread is going to be great to post in reply to any of your "findings" to completely remove any ounce of credibility or authority you think you have on the subject of hardware performance in gaming.
Careful there chief, that looks like a personal attack; the first obvious signs of a failing argument on your part I might add.I'm an amateur enthusiast and make no claims to even having a professional understanding in such an area, but wow, I'm not this thick.
Oh gosh, I didn?t realize you liked me so much. :roll:Like I said, complete lack of understanding. I'm going to save the thread as well, just so when you realize how it makes you look, you can't magically delete it.
Nope, and actually the tests I linked to backed my claims. That?s because they, unlike you, actually tested the CPU load on the cores and found in most cases there was one loaded more than others which was the primary bottlneck. Here, let me quote a portion of their conclusion again:In your dreamworld, I bet that's exactly how it works. Too bad this is reality and A)Quad cores and dual cores are very close in price B)The slightly faster/architecturally superior (more cache, w/e) dual core available at the same price does not show enough performance gain in CPU-limited situations to make a difference, more cores do.
So no, it isn?t a dreamworld, it?s an objectively proven reality.Triple- and quad-core processors still make little sense for games, it's fast dual-core processors that are the optimal choice for gaming PCs. Most games use one of the cores more actively than the others, and performance is often limited by the speed of that core. In other words, for games you'd better buy a dual-core processor operating at 3.0GHz than a quad-core processor at 2.4GHz (within the same CPU family, of course).
They aren?t architecturally limited at any reasonable settings; that?s kind of my point, and kind of why I?ve shown multiple examples of flat-lining to back these claims.Again, the vast majority of games are architecturally-limited, so why are you paying more money for the same architecture? Extra cores will show tremendous improvements, 5% difference (that's being generous) doesn't.
That?s great and all, but I don?t think Dell forums will help you read those benchmarks any better.And I see the Dell forums over at http://en.community.dell.com/forums/ . The funny thing is the "newbie" title they'll give you will be accurate.
Right here: an overclocked speed is not. That?s a direct quote from you.Where?
I see, so now using Fraps ?disqualifies? the outcome? Tell me then, how do you think those precious benchmarks were attained, the 1024x768 ones that constantly trumpet around as evidence that you?re ?isolating the CPU?, hmmm?That in itself is fallacy because people don't play games with FRAPS on (by introducing a measuring mechanism that affects the outcome you are thereby disqualifying the outcome, basic scientific principle).
That?s right, likely from Fraps. And if not from Fraps, then from game benchmark runs which according to you also don?t count because they?re ?canned?. Those are about the only two ways you can objectively benchmark a game.
Oh dear, it looks like you?ve dug yourself into quite a hole here. On the one hand you trumpet ?evidence?, but on the other it might?ve come from Fraps ?disqualifying the outcome?, or it might be ?canned?.
Keep going as this is really quite entertaining. LMAO.
I?m sure you think that claptrap looks good, but it?s really not related to what I was talking about in the slightest.FRAPS runs are a different kind of test if that's what you're referring to (see above). You'd have to make the comparison based on the same operating environment in order to gain any insight due to the variable of FRAPS being on.
?Because any idiot realizes that most people don't game at 1024x768, I don't.?Again, double digit representation of a lack of knowledge.
I?m not paying the same money. I?m paying less to get less cores, but at a faster clock speed and possibly more cache.Then why are you paying the same money for two less cores?
I know what a bottleneck is. I also know when it applies in the real-world, and when it doesn?t. You appear to know the former, but your arguments don?t seem to grasp the latter.You need to learn how your fundamental lack of understanding of computer hardware as a whole makes you think your understanding of bottlenecking makes you correct.
?Because any idiot realizes that most people don't game at 1024x768, I don't.?Double digit instance of a representation of a lack of understanding (still).
The ?fantastic? series of benchmarks? You mean the ones you referred to as ?because any idiot realizes that most people don't game at 1024x768, I don't.??No, that's in non-quadcore games. It's convenient how you've completely "forgotten" to address the fantastic series of benchmarks I've posted that demonstrates this. Amazing.
Again with the personal attacks, the sign of the impending collapse of your arguments.There goes that hope, like talking to a (very thick) wall.
*sings* ?because any idiot realizes that most people don't game at 1024x768, I don't.?*sings* douuuubbbbllleeee diigiitt*
Nope, because that?s not what I?m doing. Again, I never argued a quad at the same clock and same cache sizes is slower than a dual, because that?s theoretical impossible (although they could certainly be the same speed due to flat-lining). What I argued was (1) flat-lining and (2) the cost of quad relative to dual and how this relates to clock speed and cache sizes.I bet you thought that by agreeing with me and then changing the subject you could get away without it shown just how incorrect you are/were.
Nope, it?s not generally faster. Again, you said it yourself that's because no one's coded for it yet,. I wouldn?t actually say ?no-one?, more like ?not enough to currently make quad-core worthwhile in general terms?.So now it's not that "quad core is not faster" it's just that "quad core is generally faster but there's a GPU bottleneck."
I wasn?t wrong. Right from the start I?ve repeatedly said that if you?re that concerned about gaming performance, you should be buying more GPUs before getting more than two cores.So how come you aren't pointing out how completely wrong you are about getting a sick SLI/CF with dual core instead of a better quad core CPU leads to better performance?
You want me to correct you? Why? So that when you save this thread you can see that you were wrong?I use the terms interchangeably (I dunno, Valve does, if that's not the correct way to do it, correct me).
It?s funny you should mention Valve too; at the time they made the technology conference about starting work on multi-core support for the Source engine, Half-Life 2 was already running 17 threads. Think about the implications of this for a moment.
I?m reading a pile of irrelevant rhetoric which again appears to totally dodge the issue.Anyway, that specific quote said "multi-CPU" support, so none of those comments address the actual quote (and how correct it is), but more so change the subject because you don't have a decent answer (that's a common tactic of yours it seems).
Here?s the sequence of events for this particular example:
You first stated: In games that are multithreaded, matching or exceeding the maximum threads with cores generates the highest performance.
This inference is absolutely wrong and cannot be done, otherwise I can infer that X-Wing runs best on six or more cores.
I responded with words to the same effect: Nope, you absolutely cannot infer that because the number of threads does not guarantee any kind of performance gain. Even games ten years old often spawned around half a dozen threads yet show no benefit from multi-core. Again, simply having multiple threads provides no guarantee of performance gains on multi-core.
You responded: That's the exception, not the norm. Programmers don't waste time writing in multi-CPU support for the hell of it.
Again, totally wrong. It is not the exception given practically every commercial Win32 game ever made is multi-threaded, yet almost none show a benefit from more than one core.
As examples, Fear runs eight threads, yet doesn?t even benefit from dual-core. Quake 4 runs 14 threads, yet we know it doesn?t benefit from more than two cores.
Again, you simply cannot infer any correlation between thread count, core count, and multi-core performance gains like you were.
Fine. You summarize your points if you want and I?ll summarize mine, and we can be done with this because I don?t think we?ll ever agree. But if want to continue then be my guest.EDIT: If this still doesn't sink in, in my next post I'm just going to summarize my argument in bullet points, as this posting format is tedious.