Slashdot Mirror
Intel Delays Release of 4Ghz Chips
bizpile writes "The AP is reporting that Intel's faster version of the Pentium 4 will not be available by the end of the year as previously promised. They told PC makers this week that the 4-gigahertz chip will not ship until the first quarter of 2005. Intel spokeswoman Laura Anderson said, 'We felt by adjusting the schedule for the products, we could better meet our customers' volume requirements and their high expectations.'"
when are they plannin on keepin up with amd? lets see some high encryption with the 64bit procs
Intel is still paying for their decision to go with the netburst architecture IMHO.
They wanted to be able to crank the megahurtz and use that as a PR device (well, not only that but it helped them).
Of course they are also having problem with the 90nm tech (as is IBM -- I think that only AMD has been mostly clear sailing with that), but most of their problems have come from netburst and lack of competitiveness in the budget sector (Celerons get killed by much faster and cheaper AMD chips).
Treehugger? Treehugger... Treehugger!
Probably not. If they ship the new faster chips now, the price of the mid-high range P4s out now will drop, and they wont make as much money. So they wait and keep selling their existing stock of P4s at the same high prices until most are gone, just in time for the new chips to start arriving.
If you build it, nerds will come. Soylentnews.org
I wonder if this delay is due to Intel not keeping a lid on the enormous power consumption of the Prescott core at 4GHz? Heat and power is a major issue with these high end chips, and it makes one wonder if Moore's law will finally be halted due to heat issues.
Hmm, it seems that the way to fix it is to just remove the leading subdomain from the slashdot url. For example "it.", "games.", or "apple."
It seems to work in reverse too. So you can replace the "it." in this thread with "apple." to display it in the Apple colour scheme. (If you really, really wanted to)
It should be extremely easy to have an "Only use the default Slashdot colours" option in the user preferences. HINT HINT
"Proudly Posting Without Reading The Article"
"Does this indicate some kind of problem with the further fulfillment of Moore's law (you know, for once, Moore's law failing to apply NOW as opposed to "Moore's law will stop working in 8 months) or has this just been a bad year?"
Option #3 could be that there really isn't a killer app that requires that speed. I have difficulty imagining a lot of ppl flocking to those machines right now. It is a pity for Intel that 3d cards do more for games than cpu's.
"Derp de derp."
The first time I read a story in the IT section, I immediately hated the colors. I don't mind the use of gradients, but the lack of contrast here makes the page almost unreadable.
Most 14 year olds who get space on Geocities can make a more readable (though almost always uglier) site. Not that /.'s design isn't the cutting edge of 1998, anyway...
Intel is now feeling some pain. They've built a brand around having more M/Ghz - which only matter superfically.
Being a multi-function device means that a CPU does multiple functions. As with ANY multi-function device, a model of CPU will do some things better than others.
X86 chips have traditionally been processing heavy, I/O weak, since hard, on-demand processing hsa been the driver of the X86 industry. (Video games, etc)
Contrast that with the Sun Sparc line of chips, or IBM's mainframe hardware, heavily optimized for I/O throughput. The needs of a rendering farm node are not well in alignment with the needs of a high-capacity file server.
Even within being "processing" demands, there is a wide, wide range. Floating point. Integer ops. Parallel proccessing. Different, even cross-compatible chips and chip lines will behave differently, performing better at some tasks than others.
But, for years now, Intel has been busy spending millions convincing the population that you can boil performance down to a single number, M/Ghz.
The cracks are beginning to show. AMD has made a solid business with "slower" (Mhz) ships that perform better. Their own Centrino line is "slower" but performs almost as well!
Intel needs to get a clue, and develop a set of benchmarks that truly show real-world performance. AMD has done quite a good job with their "+" rating. (EG, my desktop is an Athlon 2000+)
I give it 6 months, maybe a year. It'll be hard, but even Intel isn't so stupid as to put this off too long.
I have no problem with your religion until you decide it's reason to deprive others of the truth.
This is from Bernie Meyerson, IBM's CTO:
I wonder if this delay is due to Intel not keeping a lid on the enormous power consumption of the Prescott core at 4GHz? Heat and power is a major issue with these high end chips, and it makes one wonder if Moore's law will finally be halted due to heat issues.
If coders didn't make code that bloated so much, the chips wouldn't be running so hot.
If you can get a job done in 2 minutes of 4GHz processing then it'll create a certain amount of heat. If you can get the same job done with more efficient coding in only 20 seconds of 4GHz processing, then you're down 1/6th the amount of heat than not.
And you can sleep the processor or put it into a slower mode while it's waiting and paused for nothing. The problems becoming with larger and larger programs that do not much more than anything before, just were able to be developed more quickly due to sloppier coding.
My Athlon runs nearly 10 degress colder than windows, when it's running linux. I think that says something
or the shareholder are happy because they don't have to invest in newer chip making fabs but keep pumping out the older chip at a higher cost for longer...
More profit!
`find / -name "*your_base*" -exec chown us:us {} \;`
Moore's 'law' doesn't guarantee speed. It merely suggests a trend that every so often (18 months - 2 years) the amount of transistors on a chip doubles. In the past, that has meant speed because thinner wires produce less heat.
.09 wasn't going to get them anywhere. But imagine the culture at Intel where you daren't say anything to anyone about it, i.e. 'Just SHIP the thing!'
The problem isn't nearly as much to do with CPU scaling for scaling's sake - those processes continue to develop at the same or similar pace. It has much more to do with scaling for speed's sake. To Intel's horror, they've found that speed isn't scaling in a linear fashion like it used to.
It must have been a terrifying discovery for the poor engineers who discovered that
"...Well, there's egg and bacon; egg sausage and bacon; egg and spam; egg bacon and spam; egg bacon sausage and spam..."