Xref: utzoo comp.sys.ncr:528 comp.arch:18393
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tdatirv!pa1
From: pa1@tdatirv.UUCP (Pat Alvarado)
Newsgroups: comp.sys.ncr,comp.arch
Subject: Re: Terradata architecures
Keywords: YNet Bus
Message-ID: <3@tdatirv.UUCP>
Date: 3 Oct 90 18:53:48 GMT
References: <211@bilpin.UUCP> <1990Sep28.020717.22610@dhw68k.cts.com> <3944@se-sd.SanDiego.NCR.COM>
Followup-To: poster
Organization: Teradata Corp., El Segundo, Ca.
Lines: 24

In article <3944@se-sd.SanDiego.NCR.COM>, lord@se-sd.SanDiego.NCR.COM (Dave Lord) writes:
> 
> I don't think what you mean by bus and what they mean (Ynet Bus) are
> the same thing. The Terradata archetecture is a loosely coupled message
> passing system. No shared memory. Ynet is the connection along which
> the messages are passed. ByNet is similar but MUCH faster. At least
> that's my understanding.

In simple terms the Teradata (Please note the spelling) YNet bus is
not just a bus, like VMEbus or S100, it is a proprietary intelligent 
bus that has been patented by Teradata to enhance parallel processing
of database SQL statements. The DataBase Computer (DBC) is the only one
of its kind geared directly toward handling Large Databases.

Incidentally, as I pointed out, the correct spelling is Teradata, NOT
terradata. Our name is derived from the prefix "Tera" (Meaning Trillion)
and the word "data" since our DBC is capable of storing
Trillions of bytes.

-- 
  |_|   Pat Alvarado                | Ph: (213) 524-6104  FAX: (213) 524-0012
   v    Teradata Corporation        | tdat!pa1@suntzu.sun.com
 /\ /\  100 N. Sepulveda Blvd.      | uunet!edsews!hacgate!tdat!pa1
/_/ \_\ El Segundo, Calif. 90245    | pa1@tdat.teradata.com