NotebookForums.com › Forums › General Notebook Discussions › Notebook Forums - General › I feel sorry for Intel... NOT!!!
New Posts  All Forums:Forum Nav:

I feel sorry for Intel... NOT!!! - Page 2

post #21 of 71
Sharakkhal: Those links are exactly the kind of hype I was talking about in the first place and I don't believe a word of it to be frank. Based on my own experience with HT, I'm pretty confident that disabling it gives the best possible computing performance. For instance, I've tried running two seti clients at once with HT enabled but it didn't go any faster than running one client with HT disabled. Actually, running one seti client with HT disabled was over 10 hours faster completing one dataset compared with running two seti clients with HT enabled. A real dual CPU system beats a HT enabled system hands down on everything, including heavy multitasking.

And you don't need both 64-bit OS & 64-bit apps to make use of 64-bit, especially since 32-bit apps actually runs both faster & smoother on a 64-bit OS.
post #22 of 71
Thread Starter 
Quote:
Originally Posted by Sharakkhal
Feel free to read and learn how your thinking is flawed:
http://www.intel.com/business/bss/pr...g/overview.htm

Hyper-threading - Windows XP can uses this to speed up multi-tasking by simulating 2 CPUs and the OS assign which tasks run on which virtual CPU, allowing 2 tasks to run at once. The programs do not have to be recompiled for this to occur, however, programs can be recompiled so that different parts of the same program will run at the same time on different virtual CPUs, just as they would in a dual-CPU PC. This also works with XP Home, unlike you've posted previously: http://www.intel.com/support/platfor...id=ipp_htm+os&

64-bit - A 32-bit OS and existing apps can run on it, but why? To make use of the 64-bit, both OS and apps must be recompiled.

Ok first off 64 bit is the future there is no debating that. Microsoft will support AMD64, LINUX supports it now and since Intel copied AMD's instructions, they'll support it too. The only argument is how soon 64bit will become useful. AMD would like you to think it's sooner, Intel view is later.

Second, developing for AMD64 is easier than people think because it is just an extension of the 32 bit architecture. Because of this ease it is cheeper and quicker to develop for. That's why it has become more popular than the Itanium whos code has to be developed from the ground up.

As for Hyper-Threading, just because you have it doesn't mean it will give you see a performance boost. Porgrams need to support it and when they do you will see a gain. Also if you're not into heavy multi-tasking you won't need it at all. In the proper setting HT is a strength for the P4 and in others, it's affects are moot.

Lastly, like snoor said HT is technology which will become redundant once dual cores come out. Chips that support it will most likely become the budget Celerons of tomorrow.
post #23 of 71
Quote:
Originally Posted by Roarak
I hate brand loyalty, it ends up hurting everyone.

Intel isnt bad, The Northwood was a great proc, and the P-M is great as well. The A64 is fantastic as well, awesome gaming performance. If i where buying a desktop right now it would definatly be build around an A-64.

Dont sell yourself short, support what performs the best, not which company makes it. Make the companies duke out trying to create the best product for us consumers.
So true.

People act like these companies are their best friends. Bottom line is that they wouldn't hesitate to bend us over in a New York minute to get every last dime out of us.

AMD charged more than Intel back in the 1GHz race. A 1GHz Athlon cost MORE than the P3. Why? You could hardly find an Intel piece, and AMD could get them out. So if you wanted a 1GHz proc, guess who you had to go to?

Buy what you think is best. If you like AMD's offering, buy it. If you like what Intel offers, buy it.

I think this comic sums it up best:

Pic
post #24 of 71
Quote:
Originally Posted by Rustican
The reason Intel pushed higher clock speed so much was because AMD was always nipping at their heals. Intel makes great products and has the best engineers, the PM is a testament to that. The reason Intel is in trouble today is because management and marketing pushed for the higher clock appeal ignoring the engineers warnings of the limits in the P4 design.
AMD was just as guilty pimping MHz as the be all end all in processor management. When they beat Intel to 1GHz, they pretty much said "we're better because we have more MHz than Intel."

Well, once the P4 started ramping up and Intel ran away with MHz (marketing/performance aside) and AMD couldn't scale their procs as high, suddenly it didn't matter.

It only mattered to them when they had it. When they didn't, it was time to de-emphasize it.

That obviously didn't work, so they came up with the PR ratings. Some times they were accurate, sometimes they were overrated, sometimes underrated.

Now that Intel's hitting a wall and Pentium M is their main seller in laptops and people didn't get why a Celeron of the same MHz couldn't keep up with a P4, MHz wasn't going to cut it anymore. Now Intel's doing their model rating. (3xx, 5xx, 7xx). Not perfect, but it's easier to draw distinctions between lines.

AMD's going to get confusing with the XP, Sempron and Hammers all having xxxx+ ratings. Maybe they need to add the model numbers as well.

Super
post #25 of 71
Quote:
Originally Posted by snorre
Don't be rediculuous, HyperThreading (HT) is possibly the most overrated feature ever.

Software has to be tuned to take advantage of HT, by optimizing the usage of the process, but as far as I know, most applications aren’t taking advantage of it, and I think that with most current applications, it can’t be done without a drastic re-write.
Kinda like 64 bitness right now.

I disagree to a point.

For most apps, you won't see a performance increase.

However, the systems feels a lot smoother when it comes to multitasking. My PC doesn't stutter when I'm doing something like video encoding while I do something else.

There are apps that can take advantage of it. HT makes a BIG difference when I encode and convert video to different formats. We're talking at least a half hour difference.

Super
post #26 of 71
Quote:
Originally Posted by snorre
Sharakkhal: Those links are exactly the kind of hype I was talking about in the first place and I don't believe a word of it to be frank. Based on my own experience with HT, I'm pretty confident that disabling it gives the best possible computing performance. For instance, I've tried running two seti clients at once with HT enabled but it didn't go any faster than running one client with HT disabled. Actually, running one seti client with HT disabled was over 10 hours faster completing one dataset compared with running two seti clients with HT enabled. A real dual CPU system beats a HT enabled system hands down on everything, including heavy multitasking.

And you don't need both 64-bit OS & 64-bit apps to make use of 64-bit, especially since 32-bit apps actually runs both faster & smoother on a 64-bit OS.
That's true.

Hyperthreading works best when you have a "large" thread and a "small" thread accessing the processor resources. This allows the processor to work more efficiently.

Problems arise when you have two "large" threads trying to utitlize the processor resources. If they both require over 50% individually, the processor's going to bog down and you'll see a performance hit.

While HT will never be as good as a true dual processor solution, it makes a good "1.5" proc workstation.
post #27 of 71
Quote:
Originally Posted by snorre
Sharakkhal: Those links are exactly the kind of hype I was talking about in the first place and I don't believe a word of it to be frank. Based on my own experience with HT, I'm pretty confident that disabling it gives the best possible computing performance. For instance, I've tried running two seti clients at once with HT enabled but it didn't go any faster than running one client with HT disabled. Actually, running one seti client with HT disabled was over 10 hours faster completing one dataset compared with running two seti clients with HT enabled. A real dual CPU system beats a HT enabled system hands down on everything, including heavy multitasking.

And you don't need both 64-bit OS & 64-bit apps to make use of 64-bit, especially since 32-bit apps actually runs both faster & smoother on a 64-bit OS.
That's not computing experience, that's wasting CPU cycles. If you want to find aliens, watch Star Trek.

I doubt anyone would ever claim a HT CPU to outperform a dual CPU system, that's just silly. What hyper-threading does do, is allow for more than one normal program to use a single CPU more efficiently. I'm not saying you can run Far Cry and Doom 3 at the same time, but you are able to multitask better.

Quote:
64-bit support is in most cases gained with a simple re-compile of the code while HyperThreading requires a drastic re-write of the code
My response was to your misinformation. That's the exact opposite of the truth. The OS decides (or a user by giving priority, or using a third-party program to increase efficiency) which virtual CPU a process uses, not the individual program. There is no need to drastically re-write the program for that to occur. If you want the one program to use both virtual CPUs (or real CPUs) at the same time, then you have the option of re-writing the program with that in mind.

I have no doubts that 64-bit is coming, to all processor manufacturers, and I'm not on the side of any of them. Only an idiot supports one side and constantly puts down the others while trying to convince everyone else to follow that one company (without the others, there's no competition and you should know what that means). But when people who are blindly on one side or the other start spewing fanboi crap like this, it just irritates me.
post #28 of 71
We all know to what fundamentalism leads us
post #29 of 71
Beleave me, any CPU today is fast enough for multitasking!!!! Infact the test made at I think it was Aces hardware showed Athon 64 multitasking with better performance than P4 HT untill you had a redicoulous amount of applications open at the same time where HT were sighty better. That's it.

What you just said about multi-taskin is utterly BS! My old K6 desktop system was good enough to encode media, download, and play games or other tasks. etc at the same time.

Uhh... maybe he is just trolling anyway. Or I need beer


Quote:
Originally Posted by Sanna
I'm not being ridiculous. I have used P4 systems extensively, and now AMD64 without a break for a few weeks. I am able to compare by now.


Yes, however, what it really means is that you can run two needy programs at the same time instead of just one. That you don't need optimizations for - at least Windows XP seems to take advantage of it automatically.

For a real life comparison: I run Seti@home. With Hyper-Threading enabled, I could run two of them at the same time, without losing much of the speed of one individual work unit. Or I can have Seti running while in a game, and the time Seti takes to finish one work unit will be nearly the same as when I run it alone. AMD 64 simply can't do the same.

Northwood was practically made for users like me. It suits my (abusive) habits a lot better than AMD 64, which is probably perfect for those users that don't multitask, and only have one program open at a time. I'm quite happy with my laptop, but it is missing the one feature that makes my desktop machine perfect for me.
post #30 of 71
Quote:
Originally Posted by Sanna
I'm not being ridiculous. I have used P4 systems extensively, and now AMD64 without a break for a few weeks. I am able to compare by now.


Yes, however, what it really means is that you can run two needy programs at the same time instead of just one. That you don't need optimizations for - at least Windows XP seems to take advantage of it automatically.

For a real life comparison: I run Seti@home. With Hyper-Threading enabled, I could run two of them at the same time, without losing much of the speed of one individual work unit. Or I can have Seti running while in a game, and the time Seti takes to finish one work unit will be nearly the same as when I run it alone. AMD 64 simply can't do the same.

Northwood was practically made for users like me. It suits my (abusive) habits a lot better than AMD 64, which is probably perfect for those users that don't multitask, and only have one program open at a time. I'm quite happy with my laptop, but it is missing the one feature that makes my desktop machine perfect for me.

Kind of - HyperThreading increases performance by keeping the pipeline full which is effective especially if you app is multi-threaded and not contending on the same resources. Turning this on or even having two physical processors will never scale linearly.

Think about it this way. If a carpenter can build a house in 120 days, does you can put 120 caprenters to finish the same house in 1 day? Probably not - the overhead of coordinating that work costs extra. That's why people have different workers working on different areas to finish the project more quickly.
post #31 of 71
Quote:
Originally Posted by snorre
MagicRobin: Well, 64-bit & HyperThreading are very different features, where 64-bit support is in most cases gained with a simple re-compile of the code while HyperThreading requires a drastic re-write of the code. Another difference is that 64-bit support will increase performance in almost everything, while HyperThreading won't necessaily give any performance increase at all. The performance potential of 64-bit is thus pretty obvious, but the same can't be said about HyperThreading or should I say HYPE-threading?
You over simplfy the complexity of really taking advantage of the capabilities of a 64 bit system. While most 32 bit code can be recompiled by a 64 bit processor and be able to run just fine, it doesn't gain the advantage of being written to be 64 bit. For the most part the 32 bit code will have been written to deal with large chunks of data in chunks of 32 bits. That won't usually change just because you have recompiled it with a 64 bit compiler. Though, the better the code is written, the easier will be to port. But thats pretty much true with any sort of coding change.

Its important to note that some applications are likely to see significant gains from 64 bit code (i.e. video encoding), while others will see little if none (i.e. word processing). This is probably why you see today a 64 bit version of DIVX in development, but I haven't heard word one about Office 64 bit.

HyperThreading is kinda a cool trick, but its not real dual processor computing. It can allow the system to operate a bit more smothly, and that is a nice feature. Its also a great way to get the consumer software industry to start moving in the direction of multithreaded programming, BEFORE you push multi-core processors into the consumer market. Its really a quite brilliant move by intel to create a demand for multi-core proscessors. Which of course both AMD and Intel are planning in the not overly distant future (next year I believe).

DanW
post #32 of 71
Quote:
Originally Posted by Superguy
Buy what you think is best. If you like AMD's offering, buy it. If you like what Intel offers, buy it.
Quote:
Originally Posted by Sharakkhal
Only an idiot supports one side and constantly puts down the others while trying to convince everyone else to follow that one company (without the others, there's no competition and you should know what that means). But when people who are blindly on one side or the other start spewing fanboi crap like this, it just irritates me.
Heinrich pretty much sums up my point of view here:
Quote:
Originally Posted by Heinrich
I personally prefer to support COMPETITION which is the American way and to NOT support a monopolistic company. Intel makes 10x the money that AMD does and they can't even produce better chips. Vote with your dollars for more competition, it's better for all of us.
When Intel starts making better and more innovative products at fair prices I might buy from them again, but untill then I'll rather shop elsewhere in the name of COMPETITION
post #33 of 71
Quote:
Originally Posted by Superguy
Now Intel's doing their model rating. (3xx, 5xx, 7xx). Not perfect, but it's easier to draw distinctions between lines.

AMD's going to get confusing with the XP, Sempron and Hammers all having xxxx+ ratings. Maybe they need to add the model numbers as well.
AMD started using model numbers long before Intel did, just look at Opteron & Athlon 64-FX model numbers.
post #34 of 71
Don't get me wrong on this, I have nothing against AMD, they make good products for their line of business.

But nobody is copying anything !! Intel isn't copying AMD's 64bit code, they simply use through an agreement with AMD just like AMD was using the X86 code through an agreement with Intel.

You all might have noticed how good AMD is evolving in it's segment (Desktop Computing) but how it's having a hard time getting through in the Server and high-end workstation segment where Intel keeps the lead.

This is all done through agreements by both companies, and that way they are able to keep newcomers away, look at those C1 and C3 (Samuel) chips, they don't make it in any segment.

It's good to see some competition by AMD and Intel but it's all planned ahead by both companies and they use gamers and people like us to wake up the flame and do their advertisement.

Just don't be fooled, there is no underdog to support here, or maybe Cirix, AMD and Intel make good products both and they both dominate the market just like ATI and Nvidia or doing it.

For me Intel as much an underdog and AMD is.

Just my 2c.
post #35 of 71
Quote:
Originally Posted by DanW
You over simplfy the complexity of really taking advantage of the capabilities of a 64 bit system. While most 32 bit code can be recompiled by a 64 bit processor and be able to run just fine, it doesn't gain the advantage of being written to be 64 bit. For the most part the 32 bit code will have been written to deal with large chunks of data in chunks of 32 bits. That won't usually change just because you have recompiled it with a 64 bit compiler.
Actually it will, since recompiling the 32-bit code with a 64-bit compiler will enable the use of the 8 extra registers available in the AMD64 architecture and this alone gives a nice performance increase. To make proper use of 64-bit adressing you ofcourse need to modify the code slightly, but even that is no major operation as far as I know.

For more information go to this awesome resource:
http://www.devx.com/amd/Door/16009

Quote:
Originally Posted by DanW
Its important to note that some applications are likely to see significant gains from 64 bit code (i.e. video encoding), while others will see little if none (i.e. word processing). This is probably why you see today a 64 bit version of DIVX in development, but I haven't heard word one about Office 64 bit.
Yes, that's the whole point with the AMD64 architecture - easy transition to 64-bit. You only need to port those apps that benefit from higher performance to 64-bit, and those that dosen't need it (e.g. Office) remains at 32-bit. This is much better way to do it compared to Itanium systems where all applications needs to be ported to 64-bit or else you will get very poor performance, since all AMD64 processors running a 64-bit OS can run both 64-bit, 64/32-bit mixed & 32-bit code simultaneously at full speed without any performance degradation.
post #36 of 71
Quote:
Originally Posted by snorre
Actually it will, since recompiling the 32-bit code with a 64-bit compiler will enable the use of the 8 extra registers available in the AMD64 architecture and this alone gives a nice performance increase. To make proper use of 64-bit adressing you ofcourse need to modify the code slightly, but even that is no major operation as far as I know.
Until you have done it, don't go telling me how hard it is. I'm a software engineer. You are under estimating how much work is involved. Why do you think its taking so long to get out a 64 bit version of windows?

Snore, you are a zealot. You don't seem to really even understand the basics of what is involved here, yet you have made up your mind. I won't bother spending any more of my time discussing this with you, since you clearly don't want to face the truth.

DanW
post #37 of 71
Quote:
Originally Posted by ramificatio
Beleave me, any CPU today is fast enough for multitasking!!!! Infact the test made at I think it was Aces hardware showed Athon 64 multitasking with better performance than P4 HT untill you had a redicoulous amount of applications open at the same time where HT were sighty better. That's it.

What you just said about multi-taskin is utterly BS! My old K6 desktop system was good enough to encode media, download, and play games or other tasks. etc at the same time.

Uhh... maybe he is just trolling anyway. Or I need beer
I'm neither a he, nor was I trolling. Thanks for your somewhat biased response anyway

Not sure if I should respond seriously or not, but here goes anyway.

I'm glad your old system performed fine for you. But that's not reason enough to attack _my_ experience, which has been in favor of the P4. Yes, any system can multitask nowadays. But I'm a demanding user when it comes to having many programs open at the same time, and the P4 system is simply more trustworthy.

I really couldn't care less when it comes to brand vs brand wars. I really, really don't care. I am free to form my opinions based on my own experience, though.
post #38 of 71
It seems that HT is the only thing you Intel people are arguing for. HT is WAY overrated; honestly do you see any significant performance gains while multitasking compared to an athlon? I'm talking about current procs, not 1Ghz crap from 4 years ago, let's talk about the current 3.4Ghz P4 ($422 from newegg) and the athlon 3400+ ($289 from newegg). Is HT worth $133? The answer is no. End of debate lol
post #39 of 71
64 bit processing has a future, however ht is a dead end technology.
post #40 of 71
Quote:
Originally Posted by xir
64 bit processing has a future, however ht is a dead end technology.
exactly.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Notebook Forums - General
NotebookForums.com › Forums › General Notebook Discussions › Notebook Forums - General › I feel sorry for Intel... NOT!!!