Intel Reacts to AMD 135
NoWhere Man writes "Raging Bull has an article which states that Intel is having to shrink its die size earlier than expected to keep up with AMD's Athlon. "Intel couldn't afford to wait on developing a mainstream desktop Willamette chip," McComas said. "They've returned to the old tried-and-true Pentium III core as a quick fix." The new Pentium III speed grade will be among the first to use Intel's new 0.13-micron wafer processing with copper interconnect. At the same time, Intel is said to be readying a 200-MHz frontside bus to support the faster Pentium III."
Re:P3 playing catch-up? (Score:1)
(Q3 for exemple).
But the difference is not that big.
Re:Intel needs to rethink this strategy (Score:1)
I thought your idea was interesting, so I decided to compute the cost of the extra power the Athlon chip dissapates as heat when compared to a PII system of the same clock. I made calculations based on power comsumption data from
http://users.erols.com/chare/elec.htm.
A K75 core Athlon at 750mhz consumes 36.3W typically, 40.4W max.
An FC-PGA PIII at 750mhz consumes 19.5W max.
Since no typical dissipation is given for the PII, I will use maximum dissipation rates for both processors.
This Athlon consumes about 20W more than this comparable PIII. If I leave my computer on for 8 hours a day 365 days a year I will use it for
8*365=2920 hours.
Therefore the additional power needed for this Athlon system is 20watts*2920hours=58.4 kilowatt-hours. (This is, of course, neglecting the different power consumption of each motherboard.)
Assuming a cost of $.10/kilowatt hour, the Athlon 750 would cost you an additional
Assuming a cost of $.15/kilowatt hour, the Athlon 750 would cost you an additional
Clue back (Score:2)
That is substantially better than the 1% figure using open source that you pulled out of your rear end. By the end of the year it could be better still.
At current exponential growth rates Linux will be an economically significant niche for chip makers very soon. (It is already significant in their planning.)
Regards,
Ben
Re:AMD Mustang (Score:2)
>>>>>
I have a feeling the benchmarks aren't valid. They are probably testing mainstream software, which P4 at its current 800MHz clock won't do to well. If they tested 3D applications, I suspect they would have gotten very different results. P4 is meant to blow away Athlon in matrix crunching (read on, more below about that), and beat it in clockspeed (so that its performance doesn't suck in regular apps). (No, I'm not an Intel-insider (ohh, I HAD to do that
and both were dismal, other than predictably
impressive memory bandwidth (with dual channel Rambus memory). Never mind the benchmarks,
there is at least one MAJOR reason to question P4's performance - the pipeline length. P4 has a
pipeline around 20 steps to allow it to reach very high clock speeds, but this brings with it two
major penalties:
- branch mispredict pipe flush (lose 20 instructions!!!)
- instruction latency; waiting for instruction arguments takes a lot of clock cycles
>>>>>>>>
Ah but look at the upside. When doing matrix crunching (which is what I suspect P4 is built to do) the pipelines can easily be kept full. Matrix multiplies are extremely regular pieces of code, and thus
A) Doesn't have branches,
B) Is easy to parallize,
C) Doesn't introduce bubbles into the pipeline.
If the hyper pipelined design allows P4 to run at much higher clocks than Athlon, then the performance on normal apps would be about the same, while performance on 3D would kill. (Especially since SSE2 has twice the throughput of 3DNow!)
Comparing P4's double pumped ALU to Athlon, you should remember that Athlon has 3 Integer
units, and 3 Floating point units (PIII has 2 of each). On certain benchmarks, Athlon just beats PIII
silly because of this:
>>>>>>>
Athlon has 3 of each, PPro and up has 3 integer, 2 FPU. However, the Athlon's 3 FPU design is a little crippled, since every clock you can only do 2 FPU operations while the 3'rd one can only do a store instruction.
When Athlon is paired with DDR memory and is able to keep it's multiple instruction decoders (it
can issue 3 instructions per clock cycle) fed, then it is going to scream, never mind the advantages
that Mustang will bring such as it's 400MHz FSB.
A final point for you to ponder: if P4 is clock-for-clock faster than PIII (I don't believe it), then why
doesn't Intel launch it at 1.2 or 1.3GHz (vs fastest PIII 1.1GHz). A process doesn't yield such a
narrow (1.4-5 or 1.3-5) speed band, so Intel must be throwing away the lower binsplits! Why?.....
>>>>>>>>
Read above comment about how the PIIIs FPU is lower power in non-regular code.
Every indication that I can see points to P4 having been designed for very high clock speeds at the
expense of instructions-per-clock performance. AMD Mustang will launch at 1.3GHz and will be in
volume before P4. Mustang achieves it's speed more through better process technology (AMD
licenced Motorola's HiP6L copper interconnect process, and is well on their way to dual damascene
and 0.13 micron), than through Intel pipeline-achieved GHZ marketing stunts.
>>>>
Maybe, or maybe Intel sees that the future is 3D, and has designed a processor to accomodate it.
Re:Assorted rantings. (Score:1)
Yes, on the other hand, the pipeline is even deeper, so bad branch predictions are going to hurt you even worse than before. Is the Level 1 cache also running at 3GHz? If I remember my comp.arch (it's been years since I read it) by breaking the pipeline into more/smaller stages, it becomes easier to ramp up the clock rate, but you get hit harder by pipeline stalls and bad branch prediction. Compilers are getting better (as is silicon) at re-arranging operations to decrease the occurrance of those pitfalls (stalls and incorrect branch prediction) but there's a finite limit to how much the linear algorithms used in most software are parallelizable. That ALU needs to run at twice the clock rate because its pipeline is twice as deep. It probably takes about the same amount of time for an instruction to make its way through the pipeline as it does on an Athlon with the same base clock rate. You get to issue instructions twice as often, but that won't buy you much if your pipeline is empty half the time.
Again, you start off assuming that doubling the clock rate of the ALU will translate into a doubling of the operations issued per second. That's like saying that the doubling of the processor clock will double a processor's spec or Quake scores. As we can see by comparing a 500MHz Athlon and a 1GHz Athlon, that is not the case, expecially if your Level 1 cache doesn't keep pace with the core.
In the end, I think it will depend on what you are doing. If you are running an application with a small tight loop that fits in Willamette's Level 1 cache, you will see a big performance boost. If you try to simultaneously run multiple applications like Microsoft Office, you will quickly blow the Level 1 and 2 caches and the increase in performance will not be much higher than what can be expected due to the base CPU clock rate increase (1GHz->1.5GHz). Can AMD ramp Athlon's clock as fast Intel can ramp Willamette's? Maybe not. It will be an interesting race.
Re:AMD could release Sledgehammer now if they want (Score:2)
B) Essentially (given the fact that they have 14 fabs or so) they ARE omnipotant.
C) RDRAM could be a problem, but Intel seems to have gotten that figured out, and besides, they could always use SDRAM.
Intel HAS introduced products at all levels before. The Pentium MMX was an example, and Pentium II was another example. (Well, high end to lower midrange anyway.) Like the PPro and its cache problems, the RDRAM thing was simply a snafau. I mean AMD almost did with the K6. If the performance of the design had been higher, (and AMD had Intel's manufacturing capacity) then AMD would have made the introduction at all levels.
Re:Assorted rantings. (Score:2)
Re:Clue back (Score:2)
i may have been smoking crack (Score:1)
Re:Clue back (Score:2)
Re:Lovely. (Score:1)
This reeks of desperation... (Score:2)
I've been a huge fan of AMD ever since their 386 DX/40's came out. AMD has done quite an impressive job trying to keep up with Intel, even though they're always doomed to be one step behind while Intel creates and pushes new standards all over the place just to bully their competitors.
I haven't bought a single Intel chip since '94, and I can't really say I've noticed any 'issues' at all with my AMD's.
Now, my question is this... why does Intel think it can continue to get away with such devious practices (remember the FP bugs, the P3 serials?) and extrememly high markups on their chips...when you might as well be paying for a chip that may just be a step below (remember how they marked pentiums based on highest stable clock speeds rather than manufacturing them all independently for a set speed?)... Quite frankly, I don't like what Intel does. At this point, I don't think Intel really has had much going for it other than name recognition.
Click here to accomplish absolutely nothing...
FDIV? (Score:2)
Intel has hardly every had problems with bad microprocessor cores
Then who's fault was the FDIV bug in the early original Pentium?
<O
( \
X Adopt a bird today!
You gotta be kidding me... (Score:1)
B) No they are not, they cannot arbitrarily throw capacity at badly yielding parts if the income doesnt justify it... for one their shareholders dont like it, and its probably a for of dumping
And how the hell is all that capacity supposed to magically make stabile products appear? Processors and chipsets (just cause they had something stable enough to run a demo on dont mean diddly squat, on top of that they need different chipsets for different market segments) dont magically appear out of those fabs, and just throwing more engineers at development to get them done sooner has diminishing returns too.
C) Intel has limited room to manouvre due to their commitments to Rambus...
Re:Assorted rantings. (Score:1)
Research by Hennessy, Patterson, and others in the early 90s indicated that procedural and naive O-O software design produces finite levels of parallelism that can be exploited by VLIW compilers. Parallelism needs to be more explicitly expressed in the software design (with threading and OO message passing) to split the task over multiple processors. This is why 1990s research into programming languages developed languages that facilitated this approach (i.e. Self, Java). The problem is that the average developer commonly found doing applications programming in many corporations is a self-taught VB programmer who has a bit of a problem switching over to effectively using those paradigms. So if you think IT staff shortage is bad now, think how bad it will be when over half of the development staff can adjust to produce the kind of software that is needed. With Itanium, I think Intel is postponing when we have to bite that bullet, but I doubt it can be postponed forever.
What the hell are you talking about? (Score:2)
Jesus.
- A.P.
--
"One World, one Web, one Program" - Microsoft promotional ad
I don't know what they're talking about... (Score:1)
-legolas
i've looked at love from both sides now. from win and lose, and still somehow...
Who the hell keeps moderating you up so fast? :) (Score:1)
The x87 FPU in the P4 has a single instruction per clock throughput (not counting load/stores which like the K7 are handled seperately) for MUL/ADD's not unlike PPro/P2/P3 but WITHOUT free FXCH. Thats going to hurt a lot of legacy code... It certainly is going to make it lag compared to K7 for anything which doesnt use SSE/2 for its floating point calculations. It probably is even going to make it lag compared to the P3 at the same clock for code which use's the x87 FPU a lot.
SSE/2 doesnt exactly give it an advantage over K7 either, for single precision its still got the same throughput on operations as 3DNow! only with better load/store bandwith compared to the P3. And for double precision it potentially has the same number of operations per clock as K7, but its advantage in its larger number of registers is IMO negated by the limitation of needing to do everything with SIMD. Which for double precision code might not always be as easy as for 3D.
Not a good fix (Score:1)
Kate
Re:x87, SSE, SSE2... (Score:2)
PIII is first being shrunk 5% while still at 0.18 micron. This will be the 1.15GHz part, and is slated for low-volume "release" on July 31st.
PIII will also be shrunk by a move to 0.13 micron. This is the "Tualatin" PIII core that is slated for introduction mid next year, after P4.
P4 is being introduced at 0.18 micron in a 432 pin package, will then switch to a mysterious 0.18 micron 479 pin package early next year, and is then slated for a shrink to 0.13 micron also around the middle of next year.
Given that Intel are only just starting on th move to 0.13 micron (and the fact that historically they've always been well behind state of the art inn process technology), I'd take those mid-2001 0.13 micron shrinks with a grain of salt! Mid 2001 is about the timeframe for process verification/samples; I'd be VERY surprised if Intel are ready for 0.13 PRODUCTION before the end of next year.
I'm not sure where you get that Intel say P4 will be a high end part. They intend P4 to replace PIII, and PIII to replace Celeron. It's not apparent that P4 adoption will be fast though because:
1) It will intially be Rambus only until Via produce a DDR chipset and fight Intel in court for the right to market it (thay have stated this is what they intend to do. Intel themselves have a legal agreement with Rambus that prevents them from making DDR chipsets for P4 .
2) None of the Taiwanese motherbaord makers have expressed interest in making P4 motherboards, because of the short life of the initial 432 pin package. They will at least wait until the 479 pin package, and maybe until Via's DDR chipset is available.
Re:Assorted rantings. (Score:1)
Can we agree on the fact that the Wiliamette doesn't exist yet?
First, it take full advantage of SSE (which is 128bit) to be able to multiply 4 floats in one operation.
Unfortunately, the software it's running doesn't. Look how much ISSE/3D-NOW! software is out there right now. And as you point out later...
Willamette is faster per clock for SIMD, slightly slower for regular FP, but the clock ticks twice as often.
The "clock ticks twice as often" part refers to the core "integer unit" only, not the fp unit. The "ALU" literally is [hardwarecentral.com] the integer processing unit. The fp unit is what will get the most press, though, and may well be slower than in the Athlon. The "integer" and SIMD performance will both be excellent, I agree. But the fp performance will sell any new chip, since we already have more than enough integer performance and SIMD only has limited support. Unfortunately, Williamette seems to fall down in that particular area. But who knows for sure, right? What I really want to know is how the Williamette deals with its 20-stage pipeline. Williamette seems to be designed for high clock speeds, which is the #1 selling feature for CPUs. But there's got to be a major penalty for mispredicted branches with a pipeline that long!
Re:AMD Mustang (Score:2)
I don't doubt that P4 will excell at some particular tasks. If used with dual-channel PC800 RDRAM and an SSE2 optimized application, I believe it will be able to turn in some impressive FP numbers. However that doesn't mean it's going to offer good general purpose performance, or perform well on legacy code.
P4 won't beat AMD on clock speed. 1.3/4GHz P4 will be up against 1.3/4GHz Mustang this year, and both will be at 1.5GHz in Q1 of next year. Maybe technically Intel will launch the 1.5GHz P4 this year (just like, technically, they launched the 1GHz PIII back in march), and Dell will sell 3 of them.
P3 playing catch-up? (Score:1)
The biggest problem will be the price. That is why I think the Athlon has done so well all this time. For 50% less money, you get a chip that performs only 5% worse than the intel equivelant. I think that is why most people, myself included, like Athlons.
Re:Assorted rantings. (Score:2)
What you really want are languages like High Performance Fortran that have the programmer declare segments of code that can be executed in parallel (not quite the same as threads).
Heh (Score:3)
AMD's doing a lot right, but there are a couple of additional things they need to do. One is to get the damn SMP chipsets out. They're not going to break into the lucrative server markets without a strong SMP offering.
Another thing they really should do is devote an engineer or two to hacking AMD specific optimizations into GCC. Intel realizes the value of this and is quietly working toward getting heavily optimized compilers in place for Itanium. AMD is sadly lacking here.
AMD is going to have to scramble if they're going to stay ahead of Intel in this race.
Re:Lovely. (Score:1)
The second SSE2 pipeline does not do FLOP's (Score:1)
This is an old rumour prooved false for quite a while now, it has a seperate 128 bit LOAD/STORE unit which can kinda count as a seperate pipeline. But its max FLOP's per cycle is still 4 just like P3/K7.
See http://developer.intel.com/design/processor/futur
Re:Lovely. (Score:1)
fdiv_bug
hlt_bug
sep_bug
f00f_bug
coma_bug
"long, strong track record", huh?
Will we ever be able to buy one? (Score:1)
Why you should wait for the new chip... (Score:2)
Seriously, if you want a computer that ages gracefully it is far more important to buy extra RAM and hard drive than the fastest chip. A 30% difference in chip speed begins to feel very unimportant when you hit swap and you cannot install anything more on your computer...
Cheers,
Ben
Re:This reeks of desperation... (Score:1)
Because the potential x86 CPU market is larger than the production capacity of Intel and AMD combined. Right now, they are both leaving lots of money on the table.
In the situation where you are selling all the product you can make, why would you do? I'd keep the prices high, especially if I had a top notch reputation (true or not), and enormous channel to move product.
On the other hand, if you AMD, and you don't have good OEM relationships (for very good historical reasons), it makes sense to eat some of the profit now and build up long term customers for when the lean times come.
Anyway, your post reeks of the usual Slashdot pro-underdog Winner/Loser dichotomy. In this market, both AMD and Intel are 'winning', unless your only concern is the dick-sizing going on at the very high-end of the lineup.
--
Re:200MHz FSB...Everything is going according to p (Score:2)
In the next few days (from now)ALI supposed to release his DDR chipset for K7. Later AMD will release his AMD760 chipset (with DDR support) and then AMD760M aka SMP.
Sometimes in Q4 AMD supposed to present Mustang that will have up to 2Mb of L2 cache (while teoreticlly I belive he can have up to 8Mb) and will start ramping from 1.5GHz
The n there is also have a bunch of mobile CPUs (Corvete aka mobile Tbird and Camaro aka mobile Duron) with powersaving technology.
And then sometimes in 2001H1 AMD should present Sledgehammer, thier dual core, 32 and 64 bit capeble CPU with LDT controller ondie (that possible will allow creation of N-way SMP systems(where N > 1
Please read carefully (Score:2)
It has a nice big chunk of the server market. That is not counted in this figure.
Given as little as 50% growth/year (observed growth has been exceeding 100%), it will be hitting 10% in a couple of years from now.
Given current trends in 2 years we could see an absolute majority of CPUs that are being sold running Linux in the embedded space. Linux looks to again be a significant portion of the small server space. Clustering technology has already made it viable for a lot of high performance computing tasks, and even in its weakest area - the desktop - it looks like it will have noticable penetration.
Of all of these initiatives the weakest is the desktop. OTOH the gaming market is quite aware that Microsoft's long-term game plan is to kill the Win9x line whenever it can. Given the choice between Linux and NT for a gaming platform, there is a real chance that Linux will win.
And yes, the chip companies are quite aware of these trends and make plans accordingly. Why do you think that Intel has been so supportive of Linux on the Itanium?
Cheers,
Ben
Re:DDR is something to be excited about (Score:2)
AMD's Athlon has a 200/266MHz FSB and can use DDR bandwidth. PIII has a 100/133MHz FSB and will get very little (maybe zero) gain from DDR.
We'll see. Typically, 80% or more of memory accesses are in cache. That's maybe a low number, but we'll work with it. Let's assume the DDR really doubles the bandwith. So now 20% of your application is going to be twice as fast. That's a whopping 10% speedup, which is hardly the same as doubling.
Yes, but... (warning, long) (Score:4)
...honestly, I could give a damn about Intel and AMD ramping their core speeds up (which is really what is driving the move to a smaller die size).
In a modern PC, the processor isn't the bottleneck for 99% of the work you're doing. Unless what you're doing can fit in the L2 cache, the processor is going to sit and wait for it. Now, modern L2 cache architectures are getting pretty good, and the hit rate is now approaching 90-95% for most stuff, but think of it this way: a L1 cache miss (which is quite common) incurs a 4-6 cycle wait, while a L2 cache miss can incur a 50-70 (to as much as 100-200) cycle wait. Ouch!
Realistically, virtually all "CPU-bound" applications these days are also memory-bound, too. Quake, Photoshop, file-compression, and others typically thought of as relying on the CPU exclusively actually suffer greatly from the constricted pipe into the CPU core. Only stuff like crypto-cracking and maybe batch rendering are truly CPU-only-bound.
Also, especially with graphics (which is one of the most CPU-intensive operations left, and for which higher-speed CPUs are generally targeted first), the trend is to specialized co-processors (the GPU), since the I/O and memory limitations of the current PC architecture make improvements in the CPU of limited help to the graphics subsystem. Take a good look today: it's a far better thing for your Quake performance to replace that 2-year-old video card than it is to replace the 2-year-old CPU. And, given which is cheaper, which do you think people will do?
I'd love to see Intel and AMD quit spending all their money (or the vast majority of it) on speed improvements, and dump a huge amount of it into redesigning the PC architecture. Honesly, I think there is a huge amount of $$ to be made in the chipset integration market. Intel has done this to a certain extent, and now owns probably 60% of the primary MB chipset market. However, nobody is doing anything interesting.
AMD has made a step in the right direction with the adoption of the EV6 bus, but Intel is still running the GTL+ bus, which sucks. I'm talking about as a bus architecture, not comparing MHZ of the bus.
I'd love it if I could buy a 600Mhz PC with an advanced memory and I/O subsystem (maybe like that on the SGI O2 or VisualWorkstion series). The key here is that the push has to come from Intel or AMD. They're the only ones who can design the CPUs to take advantage of such a design. SGI's problems (besides internal ones to the company (like no clue about how to sell into the NT market)) were that the CPU was still a "typical" CPU, and the custom chipset had to work around its limitations.
If AMD or Intel really wants a leg up on the other (and I'm not talking about "My latest CPU is 3% faster than yours, for the 1 month until you introduces your next one" crap), they should:
If AMD and Intel ever want to do something besides make desktops and small servers, they have to change the PC architecture. Maybe Merced and Sledgehammer will do that, but I'm not optimistic.
Hell, even the high-end UNIX vendors could take a page from the Mainframes. Ever wonder why the 'frames haven't died? Batch-processing my good chap - I can get a 'frame with equivalent CPU power to a vanilla Pentium that will go through 100,000 jobs/hour, where a 8-way Sun E3000 might do 10,000/hour, and a quad Xeon maybe 4,000/hour. It's all about the I/O throughput.
I'm looking forward to the day when my PC isn't of an identical design to the one I bought in 1990.
-Erik
Re:DDR is something to be excited about (Score:2)
We'll see. Typically, 80% or more of memory accesses are in cache. That's maybe a low number, but we'll work with it. Let's assume the DDR really doubles the bandwith. So now 20% of your application is going to be twice as fast. That's a whopping 10% speedup, which is hardly the same as doubling.
Yeah, but the 80% of your memory accesses from cache don't take anywhere near 80% of your processing time. Cache is so much faster that your 20% or whatever from main memory is probably taking more time than the 80% from cache. So now most of your application is going to be twice as fast. That is an impressive speedup.
Of course, like you, I'll wait and see. Theory and practice don't often agree. :-)
Java vs. VLIW (Score:1)
High Performance Fortran has VERY limited use outside of the scientific community (and probably within it these days as well). Microsoft Word is unlikely to run faster if you rewrite it in High Performance Fortran
Let's clear up some things (Score:3)
It's *way* too early to say this for sure. Willamette isn't even in production yet, and won't be out for a few months. This means it's not terribly meaningful to compare it to the Athlon, since the Athlon is out *now* and will be out in even faster versions by time Willamette ships. Now, I happen to think that Willamette will *probably* be a decent amount faster than the Athlons once the part is actually shipping. But it's a little early to say whether it will be a "lot", or just a bit.
Also consider that AMD and Intel's product schedules are offset by several months, such that they are playing leapfrog. AMD's jumped ahead with the Athlon, and Intel is likely to hop ahead with Willamette (once it actually comes out, which isn't for a while since they are moving the P3 down to
Sledgehammer IS AMD's next chip. It will HAVE to save it in the 32 bit market. It is simply a 64 bit x86 chip, not a new architecture like Merced. As such, it has a similar place to the Athlon as the Athlon did to the K6
AMD has a couple of new chips in the works. One is aimed at the desktop, and the other at high-end workstation/server environments. The desktop chip is code-named Mustang, and is a 32-bit x86 chip. The server chip is Sledgehammer, which is a 64-bit extension of the x86 instruction set architecture. Sledgehammer is NOT their next desktop CPU! Sledgehammer is designed to compete against Intel's Itanium (formerly Merced), a 64-bit VLIW-like CPU. The Mustang will be AMD's competition to the Pentium4 (aka Willamette).
First, it take full advantage of SSE
Well, OK, but this requires special processor-specific coding in the software to reap any benefits, and so you only get SSE in certain apps that choose to support it (like Photoshop). Whereas the Athlon has a significantly faster FPU without need to recompile the software. Plus AMD has 3DNow, which offers many of the benefits of SSE. Granted, 3DNow isn't as powerful as SSE, but since the regular FPU on the Athlon is faster the advantage may swing in either side's favor.
Additionally, it runs the ALUs at 3 GHz
The double-speed ALUs may not provide a really large benefit, since that's only one pipeline stage of about 20. If the other stages can't keep up, you may not see the benefit at all, or maybe only partially. You certainly won't be getting the equivalent of a 3GHz CPU. Besides, the ALU often isn't the bottleneck, memory accesses and waiting for results of previous instructions often are. I suggest we all wait and see for benchmarks once Willamette/P4 is actually on the market before we speculate much on this one
And keep in mind the leapfrog effect I mentioned above. AMD is by no means out of the race once Willamette comes out, even if Willamette does do the 30% better than the P3 like Intel claims it will (which it may, it's got some really new and cool features, such as the "trace cache"). Should be a fun battle to watch (almost as much fun as watching those prices drop
Ah, screw 'em... (Score:1)
Just this week, I bought an ASUS K7V with the VIA chipset supporting 200 MHz Front Side Bus and an Athlon 800 (Best price to performance for the nonce). No Intel at all (Maybe some of the smaller chips, but none of the main features.)
If Intel wants to go to sleep, so be it. It's nice that there is competition in both the hardward and OS arena (aka, this box is running Linux, not any sucky overpriced Win2K stuff...)
Re:Ah, screw 'em... (Score:1)
Mozilla: All we want is a fucking usable kick-ass browser. Don't lose your focus!!!
Re:200MHz FSB...Everything is going according to p (Score:2)
What else? Obviously SMP support will be nice... Anand [anandtech.com] (not to mention myself) is expecting them to be out before the end of the year.
Hmmm... one last thing of course (save the best to last). DDR support. If DDR can manage to be less pricy than RDRAM (which it should) then Athlons will blow the pants off Intel. According to this conference call summary [amdzone.com] AMD's "next gen" supports DDR... whether that means Mustang or the current crop I really don't know. The Anandtech article suggests that it will be for Mustang.
So what's next for AMD? They are about to show Intel just how wrong they have been. We will see a DDR SMP Mustang compete with Intel. Let's see how they like that???
-rt-
Re:Heh (Score:1)
I agree - I buy a lot of dual's, dozens at a time, and would much prefer to by AMD .... but they have to be as cheap or cheaper at the low end. I buy the cheapest cycles out there - I'm continually trying to guess the peak of the (daily) all up system price/performance curve.
The problem I see with future AMD SMP chipsets is that they are NOT going to be main-stream - the AMD FSB is point-to-point - that means the chipset needs about 100 odd pins per CPU - mainstream (1 cpu) chipsets aren't going to have those extra pins the SMP chipsets are going to be a low volume (and as a result probably more expensive) item. I worry that when they're finally here there will be no point in buying them because there will be no advantage
Intel's problem: Moore's law. (Score:2)
According to this article [theregister.co.uk], Moore's law suggests that processors should be shipping at 800 MHz now... the fastest speed that Intel is currently shipping in volume. Intel seems to be stuck in their monopolistic mode of thought, which dictated that they could determine that clockspeeds would be set by Moore's Law.
AMD has no such hallucinations... and benefit from a new point of view.
-rt-
Re:AMD is good (Score:2)
Depends on your definition of kicking ass, I suppose. Athlons are cheaper, yes, and just a hair faster, but we're not seeing any big breakthroughs here, like x86 compatibles running in the power range of the PowerPC chips, or a major, major price drop.
In some ways, we're just seeing a pissing contest at the high end and not much to get excited about. (People who buy new video cards every three months and overclock CPUs like crazy will of course be offended.)
Re:Assorted rantings. (Score:1)
Arguably, they do, and it's called the Athlon. The Williamette isn't out yet, and its specs are a not necessarily impressive (e.g. only a dual-pipelined FPU, compared to the three FPU pipelines of the Athlon). Of course, it could turn out to be an excellent preformer, but unless it's substantially better than the Athlon, AMD need not worry so much.
If Williamette is slower or equal than the Athlon clock for clock, then AMD has no problem (obviously). If it's a bit faster, there's still no problem, since AMD is used to selling its chips a lower price and still making a profit. That's what it's doing right now. If Williamette is far better than the Athlon, then AMD has a problem.
Even then, AMD's Sledgehammer is a wildcard. Although it's a 64-bit chip, it is supposed to have good 32-bit compatibility (unlike the Itanium, for example). I wouldn't count on it to save AMD in the 32-bit market, but even if Williamette kicks ass, AMD may have an ace up its sleeve.
Again, though, AMD's problems start when Williamette is released, and only if it's a good architencture.
Competition is good (Score:5)
Re:What would a couple of good compiler dev's cost (Score:1)
Re:AMD could release Sledgehammer now if they want (Score:1)
That's why AMD yields 12x as many GHz Athlons as Intel does for its GHz P3s.
B) Essentially (given the fact that they have 14 fabs or so) they ARE omnipotant.
Only 5 of which have been upgraded to
I would also like to point out thay AMD has MEGAfabs.
C) RDRAM could be a problem, but Intel seems to have gotten that figured out, and besides, they could always use SDRAM.
They cant. They have a contract with RAMBUS saying they cant switch back. This is why VIA is more important to Intel then they like to admit.
Re:200MHz FSB...Everything is going according to p (Score:1)
It also seems to be that if Intel did go to a 200mhz fsb, then AMD will be able to go to something higher very easily. Such as the end of this year when they go to a 266mhz fsb.
Re:hey (Score:1)
Re:hey (Score:1)
Re:Yes, but... (also long) (Score:2)
- 128-bit memory bus @ 640Mhz SDR or 320Mhz DDR. As far as I know, nobody is getting good yields on 200Mhz DDR parts at this point.
- 256-bit memory bus @ 320Mhz SDR or 160Mhz DDR. IIRC, most designers aren't using 256-bit data paths because of signal noise.
- 2-channels of RAMBUS would have to run at 1250Mhz -- that's PC2500 RDRAM.
So, I'm afraid that 10GB/s *anywhere* is a bit too optimistic. And one of the problems with updating the PC design is cost: while the chip manufacturers might be willing to fork over the dough for a higher-speed chipset, only people who are building new systems with no legacy peripherals will buy an entirely new chipset. And even small increases in cost seem to cause a lot of technologies to languish - how many 66Mhz or 64-bit PCI cards or slots do you own?Well, think more before ranting. (Score:2)
> Most importantly, the ALU's are
> clocked at twice the core speed, so >you have your integer and FPU units running
> at 3+ GHz.
1) ALU == Arithmetic and Logical Unit
It does Integer math, so no the FPU isn't clock doubled.
2) Yes, the ALU are clock-doubled, but they are also "pipeline-doubled" in effect they use also twice as many pipeline-stage so they run in about the same time.
It's great for some particular kind of code, but it's not the killer thing you made it.
The trace cache is insteresting though.
B) Do not forget that Intel is pushing for the expensive Rambus whereas AMD will surely use DDR SDRAM. Will Intel allow VIA to make DDR chipset for their P4?
It's not sure, they would risk being sued by RAMBUS shareholders, I think..
Re:Amd is good for the industry. (Score:1)
Re:AMD Mustang (Score:2)
We'll see. (Score:2)
Take this rumor with a grain of salt.
Chas - The one, the only.
THANK GOD!!!
Re:Heh (Score:3)
I'd love to see optimizations go into the compilers. Things that have had optimizations (I mean real optimizations not what you see in most games) for the Athlon as well as for the Intel systems show the Athlon chips being 50% faster than the Intel system clock for clock.
Only integer ALU is double pumped (Score:1)
As for games and 3D they rely a lot on floating point, and in Williamette's case they rely on SSE because its standard FPU is rather lame AFAICS. How well it will do in gaming integer code, dunno. The extremely fast latency (0.5 clock) on some integer instruction could help on mainly serial (pointer chasing?) code, would that for instance help much on BSP code? But you are not going to get 4 ALU instructions per clock throughput anyway, the trace cache can only supply 3...
Why Intel would give away its bus design, maybe because they are locked into a very restrictive deal with Rambus?
Re:Assorted rantings. (Score:2)
That argument still seems a bit week.
Lets see.. I run Photoshop on the lower power 1Gig Athlon. Then I go run it on a 1.3Gig willamette... Am I going to SEE that much of a difference? I mean im all for more power and more bandwidth, But I mean were not even coming CLOSE to doing 10times the speeds now or nothing. A move from a p60 to a k7-1000 thats an event. A move from a k7-1000 to a willamette Is that such a big deal? Really? Gee quake runs at 150fps not 130fps now.....? Point? I paid for the willamette with my firstborn and now my photo shop filters run 10% faster! Well pat yourself on the back there.
Hmmn.. I just dont see how that argument is relevant. Granted I STILL want speeds to increase I just dont think that its going to be such a ground shaking change... The numbers the big ones are no longer so exciting. Oh yay I got a 2gighz chip.. Its just lost some of its excitement and or use becuase now you run into people with systems that do everything they want and have enough computing power to do so in the near future (Given Software doesnt get to much slower.....)
Jeremy
If you think education is expensive, try ignornace
Re:Assorted rantings. (Score:1)
Oh I should mention their have been some early showings of the engineering P4 with benchmarks that have appeared onlne (though I'd have to go search for links). They show how badly the current situation for P4 really is (even considering it's engineering sample nature). P4 was benching as if it was a 900 Mhz chip when it was clocked at 800. I think their fall backs to older simpler technologies that allow them to clock so high has lead to substandard performance clock for clock by a large margin & Intel had to double pump the ALU's to simply keep almost even when they relaized the penalty for gettign the chip to clock higher.
Now that's an ssumption, but so is the fact that a 1.5 Ghz (3 Ghz internal) P4 is going to be such a great chip and will have just so much muscle behind it as you are claiming. Now not to be rude, but my assumption is based on an engineering sample I've seen benches of. What is yours based on other than Pro-Intel Bias?
Re:P3 playing catch-up? (Score:2)
Re:Assorted rantings. (Score:2)
1) It illustrated Intel's trickle down business model, where the absolute high end is absurdly priced.
2) They had to produce their own SRAM, and had bad yields on the SRAM. However because of the design, bad SRAM meant that the whole CPU had to be discarded. (They weren't tested until they were fully assembled.)
AMD comfortable ahead? (Score:1)
- Celerons run @ 66MHz FSB today
- P3's run @ 133MHz FSB, soon-to-be 200 MHz
- Duron runs @ 200MHz FSB today
- Thunderbird runs @ 200MHz FSB today, soon-to-be 266MHz
Given these numbers, it looks as though Intel is placing the P3 to compete with the DuronSoon to be a duron-owner,
DragonWyatt
How about Cygnus? (Score:1)
Re:Competition is good (Score:1)
Re:Assorted rantings. (Score:1)
But where are they? (Score:2)
"Where's my P4?" "It's right there." "Where? I don't see anything." "Of course not, we've shrunk the die to microscopic size." "So how come my computer doesn't work?" "Uhh.... that's a known bug. We'll have a patch out in a few weeks."
What a concept... (Score:1)
_/_
/ v \
(IIGS( Scott Alfter (remove Voyager's hull # to send mail)
\_^_/
Multiway Athalons / Thunderbirds (Score:2)
However I did notice a little sidenote on ZDNet today which reads
Right now, "the priority is for a two-way chip set solution," an AMD spokesman said.
Meanwhile, Alpha Processor Inc. may step up to the plate. API is developing 4-way and greater chip sets for Athlon.
I think i'll hold off replacing my Celery 300 (@464 of course) for a little while longer for a dual Tbird. Certainly I've read that the athalon architecture is closer to the Alpha architecture than that of intel and should lend itself to far superior smp.
AMD returns serve. (Score:1)
Re:Assorted rantings. (Score:1)
My best way to explain why is to retake a look at the actually Integer & FPU units again to see why it's not doing so well. First thing you coem across is that the Integer pipelines are doubled but the fpu isn't. This has been reported a few times if you visit such places as JC's PC News or Ace's Hardware. IF that's changed the numbers didn't refelct it in the engineering sample as the number were lower or equal to a P3 in all fpu tests. The one up for the P4/Willy is that most apps don't use SSE2 yet, so it may see more improvement later when more things start using SSE2 instead of plain SSE.
Just to make sure I wasn't full of it I went and relooked up a few things that suggested exactly what I just said. The P4 flew in Integer apps (though only a bit higher than rated compared to a P3), but bombed or stayed equal to a P3 in FPU intensive tasks. Now ok this is based on a engineering sample and thigns can allways improve and or change, but right now it's showing a high lack of that 3D performance you want, well except for showing that AGP makes more sense on it than any previous platform (he tested using a Geforce 256 for the most part and got numbers higher than normal that didn't seem to have any correlation to the FPU performance, were as he didn't see the same gains if he tossed in a PCI graphics card). I'll wait and see, but I don't think Intel is answering your prayers this time.
Re:What would a couple of good compiler dev's cost (Score:1)
Re:AMD Mustang (Score:1)
You could imagine Intel licencing it from HP to be used in their compilers. An advanced compiler could just enable dynamo for inner loops. Thus, the irregular code wouldn't get the speed penalty implied by the interpretation, and the compiler could provide valuable hints to the Dynamo system.
Compiler writers, what info would you like to see given to dynamo? Hrm. I've half a mind to ask comp.compilers this.
Re:P3 playing catch-up? (Score:1)
The new thunderbird parts change that. The Athlon beats the PIII on most benchmarks (not all mind you there are a few that favor the higher bandwidth PIII cache).
Finally, the bigger reason for the Athlon being ahead of the PIII in this article has to do with clock speed. AMD is selling something like 10 times the 1GHz parts that Intel is, with only 1/8 the manufacturing capacity.
Re:Please read carefully (Score:2)
A) NT is as stable as Linux on a consumer box. Given that games crash more often than the OS, gamers won't notice increased stability. Plus, consumer boxes are usually powered down every night, so NTs "slow death" not as noticible.
B) NT (W2K that is) still has a vastly superior user experience. Easy to access help and a pleasing format (not README text file strewn all over the system.) It is easy to configure (Plug and Play works better in Win2K than it does even in 98, and generally detects devices and installs drivers correctly the first time. A sound card install in Win2K requires but inserting a driver disk. The same thing in Linux requires knowing what an IRQ is. The interface is consistant, and games don't need hacking to get working.
C) Win2K is faster and has about the same memory requirements. First, Win2K is faster because DirectX allows an application to take over the system. Also, OpenGL on NT is very mature and well developed. Plus theres more vid card support in NT. The memory requirements for both are about the same (atrociously high for both) because a productive Linux machine often requires installation of multiple redundant libraries (Netscape for example requires compat-libs in Mandrake) and the installation of both KDE and GNOME. (Since each environent has some killer apps.)
D) The developer experience on Windows is a lot better. First, Win2K has Visual Studio, a tool that puts documentation a click away, and has source browsing, auto-completion, and an array of really good debugging tools. While Linux may have makefiles and gcc, Visual Studio can use makefiles too. DirectX is a godsend, because it offers game developers DOS-like access to hardware (game developers really don't want ANY OS on the system) while still enabling them to access hardware acceleration transparently. Plus, Direct3D has more core features, is just as fast as OpenGL, and lets you take advantage of features that only a few cards support (like vertex skinning on the Radeon and GeForce2) without having to write code to utilize the propriotary extensions for each card. (IE. In D3D you write two code cases, accelerated vertex skinning is available, or not. In OpenGL you write many cases, acceleration not available, the NVIDIA extension, the ATI extension, etc.)
The problem with Linux is that it doesn't really offer anything compelling over Win2K (aside from being free) to compete with it in the consumer arena. As for Intel supporting Linux, it is not due to any technical merit of Linux. Montery is nowhere near being ready, WinNT 64 is a joke, so the only thing Intel can fall back on is to support Linux as it will probably be the only one that will run on Itanium at its debut. Intel has supported BeOS in the past (to showcase its processors) but that doesn't mean they will support it for a long time. Soon as Montery comes out, Linux support will wane unless Intel has some business reason to keep Linux around.
Re:Assorted rantings. (Score:1)
On the otehr hand AMD ahs some nice features coming out as well in future chips that should be released at about the same time as Willy is, such as a new FPU design, The LDT bus design (which btw they are giving away, something Intel never learned how to do).
By the way we aren't seeing the best the current athlon cores can do. It's been shown that when you code in Athlon optimizations (both 3dnow! & such things as prefetch) you can gain as much as 33% performance.
Re:FDIV? (Score:2)
Re:Lovely. (Score:1)
Re:Lovely. (Score:2)
Re:Assorted rantings. (Score:2)
200MHz FSB...Everything is going according to plan (Score:5)
It doesn't seem like Intel is having a good time right now, or will be any time in the future. Anyone care to speculate on what kind of processor AMD will develop by the time Intel actually releases Willamette? I was thinking that Intel would break away with the new Willamette chips because they'd be undeniably faster, but now that they're delaying them again... AMD must be seeing Sugar Plum Faeries.
-----------
Amd is good for the industry. (Score:3)
This could be a great example of how competition actually gets things improved. Of course it could turn ugly if either one of them starts pushing products to market before they are ready, still if one does that we'll always have the other, right? ;-)
Re:Lovely. (Score:4)
Re:Assorted rantings. (Score:2)
willamette... Am I going to SEE that much of a difference?
>>>>>>>
Depends on what you do. Certain filters nearly double in speed with SSE. (Photoshop doesn't support 3DNow!) Additonally, the ALUs in Willamete run at 3GHz. Yea, its safe to say you'll see a pretty big increase in speed.
I mean im all for more power and more
bandwidth, But I mean were not even coming CLOSE to doing 10times the speeds now or nothing.
A move from a p60 to a k7-1000 thats an event. A move from a k7-1000 to a willamette Is that such a
big deal? Really? Gee quake runs at 150fps not 130fps now.....? Point? I paid for the willamette with
my firstborn and now my photo shop filters run 10% faster! Well pat yourself on the back there.
>>>>>>>>
How about this. Moving from a 1GHz Athlon to a 1.5 GHz Willamette will grant you 300% more performance (theoretically) Even if you get a third of that, you've still got double the speed. Instead of saying Quake will run faster, you can say that upcoming, graphically intensive games (Black and White, Halo) will go from 20-30fps (barely playable) to 40-50fps (comfortably playable.) Or instead of taking 13 hours for your 3D animation to render, it'll take 7 hours.
PS> Have you SEEN Halo! Its un-friggin-believable.
Hmmn.. I just dont see how that argument is relevant. Granted I STILL want speeds to increase I
just dont think that its going to be such a ground shaking change... The numbers the big ones are no
longer so exciting. Oh yay I got a 2gighz chip.. Its just lost some of its excitement and or use
becuase now you run into people with systems that do everything they want and have enough
computing power to do so in the near future (Given Software doesnt get to much slower.....)
>>>>>>
I don't have enough computing power! Where's the 1 million polygons per frame games. Why do I have to wait hours to render an animation rather than a few minutes. Why does it take several minutes to preview a Premiere movie? Unless of course you're running Word, in which case it doesn't matter. Additionally, people have been using your arguements for ever. The Pentium was only 60% or so faster than a 486, but was that worth it? Most people say yes.
Re:Assorted rantings. (Score:3)
Point A) A senior VP at Intel Corporation, Albert Yu, indicated that Willamette would only be 30% faster than the Coppermine. The Willamete will not be that much faster than the Pentium III at the same clock speed. The most important thing to remember about the Willamette is Intel has decided the way to increase performance is to raise the clock speed and sacrifice IPC ( instructions per clock ) efficiency. So you can't compare this transient from the P III to the Willamette to the transitions of the 486 to Pentium. The Pentium had a much better IPC than the 486, the Willamette will most likely have a lower IPC than the P III. But the Willamette is designed to scale to very high clock speeds. You only have to look at the Willamette's pipeline to see this design philosophy. The pipeline has 20 stages; this will make it easy for Intel to raise the clock speed. For more info on how a pipeline length affects CPU performance check out this web page. http://www.aceshardware.c om/Spades/read.php?article_id=50 [aceshardware.com]. I would also like to point out that the double clocked ALU is only one stage of the 20 stage pipeline. You do have a good point about the Sse2 instructions, if Intel can get a lot of developers to use them it will make it much harder for AMD to claim they have the fastest FPU. But AMD shouldn't be afraid, they have just rolled out a new architecture that has a lot of room for growth. And I can't see Intel getting that far a head of AMD. I would expect that title of the fastest x86 CPU will change hands many times in the next year, but Intel is not about the totally destroy AMD.
Point B) I am not going to say I disagree with you it's just that I think 3d rendering is not a good example, the average computer user will never do 3d rendering outside of a game. I think that speech recognition is a much better example... something that many people would use if it worked better...
Point C) The Ppro was expensive because they had bad yields. This is the same reason that Rdram is much more expensive today when compared to Sdram.
AMD Mustang (Score:2)
FWIW Sledgehammer will sample in Q1 2001, to ship late in the year, and therefore will not be far behind Mustang.
From the P4 benchmarks that have leaked, it appears that Intel may well be the ones in serious trouble. Certainly Intel's plans for PIII don't exactly jive with it being obsoleted by P4...
Re:Assorted rantings. (Score:2)
compared to the three FPU pipelines of the Athlon). Of course, it could turn out to be an excellent preformer, but unless it's substantially better than the
Athlon, AMD need not worry so much.
>>>>>>>>>
The Williamette is a LOT faster than an Athlon. First, it take full advantage of SSE (which is 128bit) to be able to multiply 4 floats in one operation. That twice what Athlon can do. Second, the Athlon's 3 pipelines aren't what they seem. In pracice, one of the pipelines is always limited to simply doing a store operation every cycle. (ie. you can do two floating point multiplys and 1 store every cycle compared to two floating multiplies and no store on the PIII.) Additionally, it runs the ALUs at 3 GHz. It will definately be an excellent performer, because even if it meets half the projected performance, it will rock.
If Williamette is slower or equal than the Athlon clock for clock, then AMD has no problem (obviously). If it's a bit faster, there's still no problem, since
AMD is used to selling its chips a lower price and still making a profit. That's what it's doing right now. If Williamette is far better than the Athlon, then
AMD has a problem.
>>>>>>
Willamette is faster per clock for SIMD, slightly slower for regular FP, but the clock ticks twice as often.
Even then, AMD's Sledgehammer is a wildcard. Although it's a 64-bit chip, it is supposed to have good 32-bit compatibility (unlike the Itanium, for
example). I wouldn't count on it to save AMD in the 32-bit market, but even if Williamette kicks ass, AMD may have an ace up its sleeve.
>>>>>>>>>
Sledgehammer IS AMD's next chip. It will HAVE to save it in the 32 bit market. It is simply a 64 bit x86 chip, not a new architecture like Merced. As such, it has a similar place to the Athlon as the Athlon did to the K6. Also, it will have a MUCH faster FPU because it will go RISC style and ditch the stack-based FPU present in x86 chips.
Re:Why you should wait for the new chip... (Score:2)
What about your video card? (Score:2)
As for AMD optimized code, well the Windows people can take care of themselves. Alan Cox has been given a couple of nice Athalons to try to optimize Linux on. They would be idiots not to try to do similar things with gcc. Which means that with open source you will be able to take advantage of it without having to depend on someone else for binaries.
:-)
Cheers,
Ben
DDR is something to be excited about (Score:2)
AMD's Athlon has a 200/266MHz FSB and can use DDR bandwidth. PIII has a 100/133MHz FSB and will get very little (maybe zero) gain from DDR.
With CPU speeds around 1GHz and memory around 133MHz, memory is THE bottleneck for many applications. Increasing processor speed from 900MHz to 1GHz may be nothing to be excited about, particularly since the performance increase is much less than the clock speed increase. DOUBLING memory bandwidth IS something to be excited about, since it should have a HUGE impact on performance!
Re:AMD Mustang (Score:2)
- branch mispredict pipe flush (lose 20 instructions!!!)
- instruction latency; waiting for instruction arguments takes a lot of clock cycles
Comparing P4's double pumped ALU to Athlon, you should remember that Athlon has 3 Integer units, and 3 Floating point units (PIII has 2 of each). On certain benchmarks, Athlon just beats PIII silly because of this:
http://www.amd.com/products/cpg/athlon/benchmar
When Athlon is paired with DDR memory and is able to keep it's multiple instruction decoders (it can issue 3 instructions per clock cycle) fed, then it is going to scream, never mind the advantages that Mustang will bring such as it's 400MHz FSB.
A final point for you to ponder: if P4 is clock-for-clock faster than PIII (I don't believe it), then why doesn't Intel launch it at 1.2 or 1.3GHz (vs fastest PIII 1.1GHz). A process doesn't yield such a narrow (1.4-5 or 1.3-5) speed band, so Intel must be throwing away the lower binsplits! Why?.....
Every indication that I can see points to P4 having been designed for very high clock speeds at the expense of instructions-per-clock performance. AMD Mustang will launch at 1.3GHz and will be in volume before P4. Mustang achieves it's speed more through better process technology (AMD licenced Motorola's HiP6L copper interconnect process, and is well on their way to dual damascene and 0.13 micron), than through Intel pipeline-achieved GHZ marketing stunts.
x87, SSE, SSE2... (Score:2)
Note that P4 has SSE2, not SSE. Photoshop is only going to faster if/when it gets P4-specific support, which isn't likely to occur before it becomes a volume part. Intel themselves have stated that P4 will take ("3-8 quarters") to replace PIII (up to 2 years!!!), and certainly it's hard to see the initial 432 pin P4 being volume since Intel are planning to replace it with tht 479 pin part in about 6 months (gee, wonder why..). I expect P4 with it's huge 170 sq. mm (vs 120 for Athlon) die, huge power consumption and heat output, will not be a viable mass volume part until a 0.13 die shrink sometime late next year.
Unless you think I'm unduly pessimistic about P4, look at Itanium. Now many YEARS late, and currently scheduled to launch at 733MHz (struggling in the lab at 600MHz), vs an original 1GHz+ goal... Intel arn't exactly the CPU geniuses many seem to think they are! With Intel's huge R&D budget, they still produce fewer CPU patents per year than tiny AMD!!!!
Intel needs to rethink this strategy (Score:2)
Oh right, since AMD remains ahead on what is widely available, they keep on growing market share.
Intel needs to stop playing this losing game. Take the body blow, throttle back on the speed, play up reliability, point out the hidden costs of running the chips as hot as AMD runs them, then put the energy into a better architecture...
Cheers,
Ben
Re:Lovely. (Score:4)
Re:Why didn't they screw Intel? (Score:2)
Re:What about your video card? (Score:2)
As for moving 3D to video cards, it is a specialization vs. generalization thing. Currently, the geometry accelerators in graphics cards simply offload the work, they cannot feed the razterizer by themselves. Also, they only really help games. If you put these functions on the CPU, then it will accelerate other things to. For example, a GeForce might accelerate the real-time preview of a 3D rendering app, but a faster CPU will accelerate final rendering time as well. A GPU does didly for Photoshop, while a fast CPU helps a lot. Putting this acceleration on the CPU makes a lot of sense. The reason why 3D accelerators exist at all, is because razterization is a very complex process and thus hard to do well on a CPU. However, geometry acceleration is simply the crunching of matricies, and thus can easily be put onto the CPU. Couple that with the fact that the CPU will always run at a much higher clock speed, and you've got a good arguement for not moving geometry acceleration to the graphics card.
Re:Assorted rantings. (Score:2)
A) Very easy to parallelize. Thus, the P4's 128 bit dual FPU design will be kept quite busy, and
B) Has little data dependency. When crunching a stream of a few million matracies, there are no branches in sight. You can multiply out the whole matrix before you actually get a few dependencies during the adding stage. However, even those dependencies are very regular and easy to optimize. 70+% of processing power used in a games is used for graphics, the bulk of that for geometry processing. Just the kind of thing P4 will excel at. When doing 3D rendering (especially preview) it is ALL graphics. Again, very good for 3D rendering. So what happens is, that in the end, the P4 is about equal to Athlon in regular apps, and extremely fast in 3D and other types of regular data. To me, that's a BIG advantage. To sum it up, these are the advantages disatvantages of the P4.
Advantages:
-It's ALUs run at 3GHz
-SSE2 can crunch 4 32 bit numbers in each of 2 FPU pipes
Disadvantages:
-20 stage pipelines impact performance on many apps.
Net Result: A proc built for 3D. High core speed keeps it competitive with Athlon, and special architecture makes it a 3D screamer. What's not to love?
Now if those benchmarks were a test of Quake 3 framerate, then, I'm wrong, you're right. However I suspect it was a general benchmark like SPEC or Winstone, in which case those results are irrelevant.
Re:Only integer ALU is double pumped (Score:2)
Re:x87, SSE, SSE2... (Score:2)
B) Intel is lying when they say that P4 is strictly a high end part. They said the same thing about Pentium and Pentium II, and it took nowhere NEAR 4 years for them to trickle down.
C) The die shrink is happening BEFORE Willamette comes out. It is being applied to the PIII, and thus will be fully debugged by the time P4 arrives.
Take a company that has only a few RISC processors under its belt, then have them design a processer that has a design that has never been tried before. It's a wonder the thing even powers up.
Assorted rantings. (Score:4)
A) AMD is in serious trouble. It still has the sheer clock speed advantage, but doesn't have a next-gen architecture to compete with Willamete. Now if Willamete is delayed long enough, maybe they will be able to get their 64 bit Sledgehammer chip out in time, but that seems doubtfull. The reason they should be so scared of Willamete is that it is truely a new architecture. Remember the transition from 486 to Pentium, and how the 60MHz Pentiums beat even 100 MHz 486s? Well, this promises to be just as big. Not only does this signal the arrival of ultra-high bandwidth memory to the mainstream (RDRAM on high-end, DDR-SDRAM on lower end) but the Willamete architecture boasts a number of improvemnts. Most importantly, the ALU's are clocked at twice the core speed, so you have your integer and FPU units running at 3+ GHz. This promises to be an even bigger jump than the switch from 1 integer unit in the 486 to 2 in the Pentium. Additionally it introduces new instructions, and it seems that the new instruction set idea is genuinely working, since SSE actually DOES help out a lot in apps like Photoshop and 3D renderers. AMD should be afraid, very afraid. (Buyer Tip: Don't buy a new computer before the Willamete comes out. I have a friend who purchased a Pentium 233 just before the PII came out, and I remember laughing at him for quite awhile.)
B) Preemptive strike against those saying that new CPUs are useless. Go run 3D Studio on you Pentium-60 and then come back begging for forgiveness. The truth is that the bandwidth problem is just not that important for many applications. Additionally, bandwidth is getting a major shot in the arm with the coming of dual-channel RDRAM, and DDR-SDRAM. (Buyer Tip: Get DDR-SDRAM if you're going anywhere near 3D. Latency is KING!)
C) Buyers beware. If AMD can't match the Willamette in sheer performace, we may again revert to a situation like the PPro era when Intel's power proc was really expensive, and with no competition on the high end, they had no incentive to lower prices.