>I can take issue with most all of what I know since it came
>from those before me.
What a great point. The issue is not what you know or dont know, its what you proclaim to know when you don't. I'm allergic to that. You keep stating over an over hyperthreading results in instability, even when it has been pointed out to you over and over what a nonsense claim that is. If you do not know, don't spread fud, and if you think you know because you have an unstable setup, that perhaps is less unstable with HT disabled and therefore you conclude HT is definately the cause, and this phenomena has got to be universal, then that shows something about you as well.
>we're ALL FUDDING around.
Maybe you do not realize what the word FUD means.
>What FUD, I have no fear of many HT PC's locking.
By claiming there is a causal relation between HT and instability, you inflict fear (uncertainty, doubt), which is not warranted. Hence, you spread fud.
>PC's simply have fewer configuration issues with HT
>disabled since it adds to issues already there.
I've asked you before, and will ask you again: please show us half a shred of credible evidence hyperthreading results in instability, and it is therefore warranted someone owning or buying a P4 should be warry of enabling it.
>What is it about system issues that have got everyone so
>defensive?
its your false conclusions you keep posting as facts that get me offensive.
>You make assumptions about HT's perfection that is too
>intertwined to really support. I turn it on and more issues
>arise. Well, there seem to be more issues doesn't it?
Guess what; I've got an old Athlon system from a friend sitting here, with a Tbird 1400/133 FSB. When I set FSB to 133/266, it crashes every 5 minutes, sometimes it won't even boot. When I set it to 200x10.5 (1050 MHz) it works just fine. So, can I conclude there are issues with Tbird 1400 ? Using your logic, I could. People should think twice before setting it to the FSB is was designed for.. or risk instability. Makes sense no ? Unless, maybe, could it be the box has crappy cooling, inadequate powersupply or the memory doesnt support 266 DDR ? Maybe I didnt flash the bios, maybe I've got a KT133 that doesnt run at 133 Mhz ? Maybe even the chip is a 200 Mhz part and I should set a 14x multiplier ? There are plenty of reasons that cause this behaviour, and since AMD sold millions of those chips, and I've not read anywhere they do not work as advertised, common sense says something else is the problem.
>No, it simply doesn't do as much as people think it should,
>as supported by Tom's Hardware guide tests
Performance of HT has been known for a long time to varry somewhere from -5 to +15% on average. If you expected more (or less) blame your expectations. Besides, you really think this board needs your expert opinion on HT performance ? You reallly think posters here have not read two gazillion P4 reviews ?
> Is it FUD your afraid of (isn't any) or that the HT world
>has smears on its glass exterior you're somewhat ashamed of
>(shouldn't be)?
LMAO ! You have clearly not been around here for very long. I can't wait to be labeled an intel fanboy for the first time in my life; please make it happen.
> HT is perfect...right?
Not anymore than AMD64 or SSE is "perfect", its just another technology that helps performance under certain circumstances. Its cheap in die size, and has little downsides, there is nothing wrong with it.
>1.0 In a dual HT enabled system, is the motherboard seeing
>"four" CPU's? Two real / physical and two virtual?
Yes.
>2.0 If a pipeline prediction is incorrect and flushed, is
>the data in BOTH CPU's pipeline common to that processor
>flushed? If so, would this not have a double negative if
>too many wrong predictions were made?
No. Each logical processor has its own context, if the pipeline is flushed, this only affects one context. The other logical cpu is not affected.
>3.0 Would this would be a negative if you use short
>duration type desktop tasks verses longer consistent one
>where you have convinced me that HT really will benefit
>this user?
I have no idea what you're asking. What do you mean "longer task" ? I hope you do realize just opening a print dialog in word would translate in maybe tens of millions of clockcycles and the cpu might be interrupted and switch threads and contexts perhaps several thousand times between your click and the appearance of the dialog ? So please define "a long task".
>4.0 Dual core type HT enabled tasks are more server centric
>than desktop, possibly?
Tasks arent "dual core or HT enabled". Software can be multithreaded or not. Or you can run several single threaded cpu intensive apps at once. Some apps lend themselves well to multithreading, and for instance any half decent rendering program can be configured to spawn as many threads as you like. For other programs, like games, creating multithreaded code will be a lot harder. But again, there is nearly no difference between creating software that takes advantages of several physical cores or logical cores. Obviously, server software tends to be much more multithreaded friendly since it is designed to support several users simultanously, and designed to take advantage of SMP systems.
> Where are those application (most are not synthetic)
>benchmarks that show an Intel CPU beats an AMD in desktop
>use with HT enabled, and loses with it turned off?
What sort of nonsense criterium is that to judge a technology ?
> If we don't use scripted "real" applications what do we
> use to "prove" our point?
My point was never to claim hyperthreading enabled enormous speedups. My point is that it does NOT inflict instability like you claimed, unless with software that is so crappy that it will not run on SMP or CMP systems either. Creative Labs drivers are indeed a prime example or worthless coding, and are known to give problems on all sorts of configurations, which may include HT for all I know. If there is a lesson to be learned, it is to avoid Creative products at all costs, something most people here have known for ages.
Damn.. I don't think I ever wrote such a long post to defend an intel technology..
= The views stated herein are my personal views, and not necessarily the views of my wife. =