I was suffering a buffer overflow error. Itanium eh? What they heck were they thinking when they came up with that. I remember when things were named after what they did. Like the Commodore64, and the Mac512. Why not call the Itanium the intel64. What they really ought to call it is the Intel-Finaly-Got-Around-To-The-Stuff-They-Put-In-T he-SparcII
The first generation of Itanium systems, using the 460GX chipset, will be expandable with up to 64GB of memory. Generations beyond that will be able to take more memory. Higher end Itanium systems designed by the likes of SGI, IBM and HP should eventually be able to take far more than 64GB. While it may be hard to imagine 4GB or even 64GB of memory being a bottleneck to performance, when you consider SGI has mentioned plans to eventually build machines using 512 Itanium processors accessing more than a terabyte of data in main memory, 64GB of memory, let alone 4GB, begins to look rather small
Like all things "free" this service, although well intentioned, is expensive, mediocre, and unrealiable. Best of luck to them. We'll stick with our T1 and DSL.
If Linux is the target platform, which chip is better? Compiling linux in 64bit seems straightforward enough. So wouldn't the irridium be the better choice, as its less backwards compatibile? The AMD seems more virsitile, but with linux, you can compile out the 32 bit problem. Both chips seem like they'll starve on too little cache sizes.
Is the L1 cache subset redundant of L2. I assume L2 is subset redundant of the L3. Or is each cache independent? Anyone know. Sounds like this chip is going to starve on memory.
I don't think that Java is the only factor in Linux become an enterprize solution. The OS needs some work too. Linux will need to scale to enterprize hardware packages (its getting closer). However, no one can deny, that middle-tier application servers are moving to Java. I wouldn't want an OS where everything was running in java either. However, I'd rather not implement an enterprize-level distributed-net-application in exclusively C++ (actually I'd love to, it just would take 10 times as long).
Linux had better embrace java if it wants to be an enterprize OS. Java is the new choice for enterprize app/networks. Interoperability, consistency-maintainability, the java lib, debuging, jdbc, etc are all driving enterprize solutions to java. You can get 10 java engineers for every 1 C++ engineer. App servers are all shooting towards java as their solution. If the linux community fails to embrase servlet runners and excellent ejb servers, it will never achieve the enterprize-level middletier throne that it deserves. However, Sun will probably do everything it can to prevent this from happening.
Top 10 Reasons to Move to Windows 2000 Professional
1. Value You'll pay lots of money for Windows 2000 and MS support and training, increasing the value of your Microsoft stock.
2. Reliability Win2k is almost as reliable as unix now!
3. Mobility Since win2k is completely insecure, anyone can access your computer from anywhere!
4. Manageability Win2k is easier to manage and support, until you find a bug, at which point your completely screwed!
5. Performance Win2k has proven to be faster than Windows 95 (its amazing what you can do in 5 years).
6. Security You'll feel safe knowning that only Microsoft (and some russian maffioso) have ever seen the source code!
7. Internet You can be sure that our software will never comply with any of the internet standards
8. Usability Win2k has provided us with many wizards like that Paper Clip guy to make life so much easier!
9. Data Access By using roaming profiles you can access your data from any workstation, unless its not a win2k box, in which case you'll complelely hose it.
10. Hardware Win2k runs on the same '86 hardware that it always did, forcing the CPU companies to continue that ass backwards compatibility. Also, win2k fixed that NT multi-CPU bug.
I don't think Quality Control (QA) has much to do with debugging, but everything to do with testing. Debugging is an attempt to track down a problem, is almost always done by the developer in response to a bug (probably submitted by QA). Development and debugging go hand in hand. Now testing is another matter. Having developers working on testing can be a costly waste of resources.
Pure Heaven! We had it much rougher! Back in my day, Turing hadn't even come up with the Turing Machine yet. We had to think up the idea ourselves, implement it with watery dirt from the bottom of a lake, work 28 hours in the mill, and then forget how we did it, every day!
Linux.com has weekly newbie articles. Also Linux Journal occassionaly has some worthy newbie articles. Of course, nothing beats handing out RedHat cds and making 'em install linux at home.
I also say nuc-u-lear all of the time, when I intend nuclear. I suffer from a kind of dyslexia. While retardation is too strong of a word, indeed, my disability is pathological in nature. While on the other hand, your colloquial grammar and lack of manners can only be attributed to ignorance and/or demeanor. Anyway, thanks for the tip;)
This article on tech report addresses DDR with the new Athalon 760 chipset.
The hardocp article doesn't fully address overall system architecture. Although the article was interesting in is broad coverage of the memory latency/bandwidth bottleneck, I am warry of articles that don't use entire systems architectures in their performance reviews.
Slashdot Mirror
I was suffering a buffer overflow error. Itanium eh? What they heck were they thinking when they came up with that. I remember when things were named after what they did. Like the Commodore64, and the Mac512. Why not call the Itanium the intel64. What they really ought to call it is the Intel-Finaly-Got-Around-To-The-Stuff-They-Put-In-T he-SparcII
from Sharky Extreme Article
Sun Microsystems today announced their intention to lay off a third of their Marketting staff in their Solor Robotic Lab which employess three people.
1. OEM's such as VA Linux, Penguin, and hopefuls Dell and Gateway.
2. Small - Mid-Size Business Networks. Admins don't want to mess with all of the rpms and want the auto update feature, plus support.
Like all things "free" this service, although well intentioned, is expensive, mediocre, and unrealiable. Best of luck to them. We'll stick with our T1 and DSL.
Oh no! No Pot-Curling. What a shame! The best events will be covered on the internet anyway: IOC bribery and scandle, and 14-yrold drug violations.
If Linux is the target platform, which chip is better? Compiling linux in 64bit seems straightforward enough. So wouldn't the irridium be the better choice, as its less backwards compatibile? The AMD seems more virsitile, but with linux, you can compile out the 32 bit problem. Both chips seem like they'll starve on too little cache sizes.
Is the L1 cache subset redundant of L2. I assume L2 is subset redundant of the L3. Or is each cache independent? Anyone know. Sounds like this chip is going to starve on memory.
I don't think that Java is the only factor in Linux become an enterprize solution. The OS needs some work too. Linux will need to scale to enterprize hardware packages (its getting closer). However, no one can deny, that middle-tier application servers are moving to Java. I wouldn't want an OS where everything was running in java either. However, I'd rather not implement an enterprize-level distributed-net-application in exclusively C++ (actually I'd love to, it just would take 10 times as long).
P.S. Who cares about the java-language, its the lib that is sweet!
Linux had better embrace java if it wants to be an enterprize OS. Java is the new choice for enterprize app/networks. Interoperability, consistency-maintainability, the java lib, debuging, jdbc, etc are all driving enterprize solutions to java. You can get 10 java engineers for every 1 C++ engineer. App servers are all shooting towards java as their solution. If the linux community fails to embrase servlet runners and excellent ejb servers, it will never achieve the enterprize-level middletier throne that it deserves. However, Sun will probably do everything it can to prevent this from happening.
1. Value You'll pay lots of money for Windows 2000 and MS support and training, increasing the value of your Microsoft stock.
2. Reliability Win2k is almost as reliable as unix now!
3. Mobility Since win2k is completely insecure, anyone can access your computer from anywhere!
4. Manageability Win2k is easier to manage and support, until you find a bug, at which point your completely screwed!
5. Performance Win2k has proven to be faster than Windows 95 (its amazing what you can do in 5 years).
6. Security You'll feel safe knowning that only Microsoft (and some russian maffioso) have ever seen the source code!
7. Internet You can be sure that our software will never comply with any of the internet standards
8. Usability Win2k has provided us with many wizards like that Paper Clip guy to make life so much easier!
9. Data Access By using roaming profiles you can access your data from any workstation, unless its not a win2k box, in which case you'll complelely hose it.
10. Hardware Win2k runs on the same '86 hardware that it always did, forcing the CPU companies to continue that ass backwards compatibility. Also, win2k fixed that NT multi-CPU bug.
Now all Dell needs is some AMD chipsets and they'll be all set.
Like the internet, computers, higher mathmatics,...
What young is he talking about? Give the kids a little credit.CNET is reporting NEC is recalling the chips. No news on what Sony will do yet.
I don't think Quality Control (QA) has much to do with debugging, but everything to do with testing. Debugging is an attempt to track down a problem, is almost always done by the developer in response to a bug (probably submitted by QA). Development and debugging go hand in hand. Now testing is another matter. Having developers working on testing can be a costly waste of resources.
It's a Reuters report. It just happens to be posted on yahoo.
I emailed Transmeta's PR department... Wait and see if they get back to me ;)
Pure Heaven! We had it much rougher! Back in my day, Turing hadn't even come up with the Turing Machine yet. We had to think up the idea ourselves, implement it with watery dirt from the bottom of a lake, work 28 hours in the mill, and then forget how we did it, every day!
This is an open source linux help package
Linux.com has weekly newbie articles. Also Linux Journal occassionaly has some worthy newbie articles. Of course, nothing beats handing out RedHat cds and making 'em install linux at home.
Don't be, check out these guys..
I also say nuc-u-lear all of the time, when I intend nuclear. I suffer from a kind of dyslexia. While retardation is too strong of a word, indeed, my disability is pathological in nature. While on the other hand, your colloquial grammar and lack of manners can only be attributed to ignorance and/or demeanor. Anyway, thanks for the tip ;)
The hardocp article doesn't fully address overall system architecture. Although the article was interesting in is broad coverage of the memory latency/bandwidth bottleneck, I am warry of articles that don't use entire systems architectures in their performance reviews.
By A.I. they mean that stupid paper-clip guy in MS office.