Subject: | |
From: | |
Reply To: | |
Date: | Tue, 6 Mar 2001 18:00:13 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Richard and others commented:
> Or, if they are going to crip the CPU, at least drop the price
> of the initial system so low that it competes with an off the
> shelf Dell server with SQL-server for 100 users.
I would expect that one of if not *the* worst impact of running
the new A-Class e3000 at ONE-FOURTH the CPU speed of
the equivalent HP 9000 will be in choices many if not most
potential *new* customers will end up making; i.e.:
If you have existing Image/SQL apps, the ability to extend into
the intranet and Internet realms with Java, Apache, WebWise,
Sendmail, Bind/DNS, etc. is a big plus; even if all those CPU-
hungry web apps run significantly slower on the e3000 than
on the 9000 variant of the A-Class.
But if you are a potential NEW customer *without* existing
IMAGE apps, consider: You can buy a 9000 A-Class that will
run the above and most other internet apps FOUR TIMES as
fast for LESS MONEY than you can buy an e3000 A-Class.
If being on the Internet / an intranet with above "standard
apps" & etc. is an important part of running your business,
will other advantages of MPE and Image/SQL on the e3000
overcome having to pay MORE $$ to get ONE-FOURTH the
performance ??.. In most if not all cases I expect the answer
is no...
Since in the long run the e3000 has to continue to get some
percentage of new customers on an ongoing basis, I see the
huge performance DISincentive for "standard" Internet apps
compared to the 9000 A-Class (and for that matter name-
brand Win2K servers) as a major stumbling block.... So I
respectfully suggest HP needs to re-think where they set the
clock speed on the e3000 A-Class.... and soon....
Ken Sletten
|
|
|