Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: OT RE: Async I/O on Windows
Safire
is another defecatory device.
<FONT face=Arial color=#0000ff
size=2>
My own
personal reference for correctness is Edwin Newman. (He is
dead
now, and so provides little in the way of argument any
more.)
<FONT face="Times New Roman"
size=2>-----Original Message-----From: Yosi_at_comhill.com
[mailto:Yosi_at_comhill.com]Sent: Tuesday, February 06, 2001 2:16
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
OT RE: Async I/O on Windows
<FONT face=Arial color=#0000ff
size=2>"broken toilet of a man?"
<FONT face=Arial color=#0000ff
size=2>
<FONT face=Arial color=#0000ff
size=2>That's certainly an interesting phrase. We should call William
Safire...
<FONT face=Arial color=#0000ff
size=2>
<FONT face=Arial color=#0000ff
size=2>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<FONT face=Tahoma
size=2>-----Original Message-----From: Mohan, Ross
[mailto:MohanR_at_STARS-SMI.com]Sent: Monday, February 05, 2001 5:00
PMTo: Multiple recipients of list ORACLE-LSubject: RE:
OT RE: Async I/O on Windows
Another way of looking at it:
So lets say the 12 computer configuration were to have a
failure in some *single* wintel box every 7 days ..
who cares!! The shared nothing architecture
underlying the system load BALANCES users to <FONT
size=2>machines which are up .. no user would even notice ... This is how
you hit "Five Nines" at superlow cost points.
This is particularly useful for rolling new machines into
and out of the server set to SCALE AS
NEEDED...instead of buying "BIG IRON" that sits and
waits for the once a year spike in usage. (But you <FONT
size=2>get to pay for it every day!) Just as sites like DELL who will
trippple their site size for xmas than return to
fewer machines afterwards.
BUCKETS OF Money saved on operational costs ( server
contracts, electricity etc ... ) and all users
served all the time. Let's not even TALK about
the savings on "POWER UNITS" :) (Larry, you broken <FONT
size=2>toilet of a man!)
Low concurrency numbers are historically due too poor
configuration (the problem is in the application 80%
of the time)...just 'cus someone doesn't know how to
write an app doesn't mean it can't be done.
Oh, and this just in, News Fans:
The idea that it requires a highly skilled, highly trained,
expensive DBA to go create a table is stupid ...
I'll get a 7 year old to do it in a few clicks when
he gets home from school .... while the database is tuning itself, and I
am out studying for me new technical
skills...Yay!
-----Original Message----- From:
Jesse, Rich [<A
href="mailto:Rich.Jesse_at_qtiworld.com">mailto:Rich.Jesse_at_qtiworld.com]
Sent: Monday, February 05, 2001 2:42 PM <FONT
size=2>To: Multiple recipients of list ORACLE-L <FONT
size=2>Subject: RE: OT RE: Async I/O on Windows
Actually, not that it matters from what I can tell, but
Oracle is tops if you consider clustered vs.
non-clustered. It seems that Oracle doesn't even <FONT
size=2>have tests for clustered systems. I wonder what happened to the
VLDB tests in the huge DEC/Compaq Alpha
cluster? As far as
SQL (pronounced: "SQueaL") Server "blown the doors off", there are
factors that TPC does not consider. First, is
reliability. According to Oracle Magazine,
Jan/Feb 2001, p38, "...a 12-computer configuration from <FONT
size=2>Microsoft, such as that used in recent TPC-C benchmarks, is estimated
to experience a catastophic failure once every 7.5
days, according to Microsoft's own estimates."
Granted, the quote is from Oramag, but I've heard
the same from other "Industry Sources". <FONT
size=2> I know of a specific implementation
where the NT database servers would dog and/or crash
when approximately 500 concurrent users were attached (note:
"attached" <> "active") to the database. The
decision was made to dump NT for DB serving and go
with a major (HP or Sun or IBM) flavor of Unix for <FONT
size=2>it's scalability and reliability. <FONT
size=2> Second, when was the last time you
needed a 500K TPC-C from only 48 clients? From a
couple thousand, yes, but only 48? And who's gonna buy everyone
in their company a $7500 desktop PC with twin
PIII-800s in them for clients? While those numbers
are specific to the top TPC-C Compaq/MS result, that's <FONT
size=2>how all these companies get their numbers. <FONT
size=2> I'm not betting my job on TPC-C
numbers. The numbers just don't reflect <FONT
size=2>real-life situations. <FONT
size=2>And I didn't even touch upon the potential locking problems on SQL
Server, or how it can do dirty reads...
:) Just my
$.02. I need to go create some Oracle databases on HP/UX now.
;) Rich
Jesse
size=2>(heh heh heh) <FONT size=2> <FONT size=2>
I'm not sure by "single thread management" whether you mean
NT can't have multiple processes or Oracle on NT
runs as one thread. The former is obviously
wrong. The latter is a design issue inside Oracle
Corporation and the question <FONT
size=2>as to why was asked on this forum before without an answer (without
an answer I can remember,
that is).
Yong Huang yong321_at_yahoo.com
you wrote:
Asynch I/O on a Windowze box? supresses a snigger...
To the best of my knowledge there are no Windows based
system that can take advantage of this, single
thread management can be enough a problem <FONT
size=2>sometimes..
But, I may be wrong.. List?
This message has been scanned for viruses with Trend Micro's Interscan VirusWall. Received on Tue Feb 06 2001 - 14:36:24 CST