Archived from groups: alt.comp.periphs.mainboard.asus (
More info?)
There's a slight difference in the analogy your draw.
RAID 0 will result in loss of data.
A dual core CPU will not damage anything.
One of the key points that people are not addressing is that CPU's will not
continue to increase in performance as they have done in the past. The
*great folly* at the moment is that CPU manufacturers are jumping on dual
core to continue this net effect.
It won't work 'cos a dual core or cpu has never been and never will be equal
to a single of 2x (or near) the performance.
For those of us that will benefit from dual core there is no folly - just
bees knees systems. The next challenge is for programmers and program
langage designers to come up with methods that will enable easily more
effective dual core usage. Intel has been very very busy on the HT side of
this, both AMD and Intel need to put a lot of effort in to it as otherwise
the market will come to a shuddering slowdown in about 2 years.
"milleron" <millerdot90@SPAMlessosu.edu> wrote in message
news:8uerb1hna43j06dn96h6hclt6orone2pau@4ax.com...
> On Sat, 25 Jun 2005 00:58:13 -0600, "Mark A" <nobody@nowhere.com>
> wrote:
>
>>"Mercury" <me@spam.com> wrote in message
>>news:d9iu67$mo5$1@lust.ihug.co.nz...
>>> You do not include enough factors in your consideration "A fixed amount
>>> of
>>> money". Thats a horendously dumb way of spec'ing a system. If you want a
>>> CHEAP system, get one. If you want an expensive system, then get an
>>> Intel.
>>>
>>> If you want to understand better about the factors surrounding who may
>>> benefit, how and why, then read my posts. Until then you are casting an
>>> ill-informed opinion based on wilful ignorance.
>>>
>>> May the All Blacks win tonight!
>>>
>>If you want to spend $616 for a dual core CPU that runs at 2.2GHz with 512
>>GB L2 cache (each) , that is OK with me. But actually you will need to
>>spend
>>about $800 because you will need more memory for the dual core processors.
>>If you don't believe me, ask anyone who uses a dual CPU PC with Windows.
>>
>>So for about $800 you can get a AMD Athlon 64 FX-55 Processor (San Diego)
>>running at 2.6GHz with 1GB L2 cache. This will also run cooler (and
>>therefore quieter) than the dual core.
>>
>>My point is simple. The vast majority of desktop users will see noticeably
>>better performance overall with the AMD Athlon 64 FX-55 (or even 53) over
>>the dual core AMD Athlon 64 X2 4200+. Obviously there are exceptions, but
>>not as many exceptions as people would like to believe.
>>
>>Even the $475 AMD Athlon 64 4000+ Processor (San Diego) will probably seem
>>faster than the dual core 4200+ most of the time.
>>
>>Don't confuse the issue. I have nothing against spending money on a PC,
>>but
>>I like to be able to figure out which option is the best bang for the
>>money
>>(this is called financial analysis).
>>
>>I also have nothing against multiple CPU's, especially in servers, since I
>>use 4-way and 8-way servers at work all the time.
>
> Hey, Mark,
> I followed the thread with interest. There are very valid points on
> both sides of the issue, but in general I agree with you.
> Your arguments are analogous to the battles I've waged in Usenet for a
> few years trying to talk the average user out of spending a lot of
> money on RAID-0 setups. I still think they're abject folly, even for
> enthusiasts, unless they use their computer for one of the few
> purposes that actually benefit from RAID 0.
>
> I mention this because I ultimately lost that fight, and I think
> you're bound to lose this one, too. These issues in most cases end up
> being decided at a hormonal level rather than a logical one. I'm
> almost positive that when dual-cores get down to less than $250, I'm
> going to "need" one, too.
>
> Rhetorically yours,
> Ron
>
>
> Ron