You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 35.171.0.0/16 has been blocked (disabled) by ‪JJMC89‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 05:20, 2 December 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 05:38, 21 February 2024
- Expiry of block: 05:38, 21 February 2029
Your current IP address is 35.171.25.239. The blocked range is 35.171.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((Refimprove|date=July 2016))

'''Pyramid Technology Corporation''' was a [[computer]] company that produced a number of [[RISC]]-based [[minicomputer]]s at the upper end of the performance range.<ref>[https://books.google.com/books?id=izwEAAAAMBAJ&dq=Pyramid+Technology+Corp.%2C+Mountain+View%2C+CA&pg=PA34 Pyramid Unveils Disk Sharing Plan For IBM PC, Macs, Sun Workstations], By Sharon Fisher, Page 34, InfoWorld, 17 Nov 1986</ref>  It was based in the [[San Francisco Bay Area]] of [[California]]

They also became the second company to ship a [[multiprocessor]] [[UNIX]] system (branded [[DC/OSx]]), in 1985, which formed the basis of their product line into the early 1990s. Pyramid's OSx was a [[universe (Unix)|dual-universe]] UNIX which supported programs and system calls from both 4.xBSD and AT&T's [[UNIX System V]].<ref>[https://books.google.com/books?id=nDAEAAAAMBAJ&dq=Pyramid+Technology+Corp.%2C+Mountain+View%2C+CA&pg=PA40 AT&T and Pyramid will develop server line: Deal allows AT&T to remarket Pyramid Line], Page 40, InfoWorld, 16 Oct 1989</ref>

==History==
Pyramid Technology was formed in 1981 by a number of ex-[[Hewlett-Packard]] employees, who were interested in building first-rate minicomputers based on [[RISC]] designs.

In March 1995 Pyramid was bought by [[Siemens AG]] and merged into their Siemens Computer Systems US unit.<ref>[https://www.nytimes.com/1995/01/10/business/company-news-siemens-is-in-talks-to-buy-pyramid-technology.html COMPANY NEWS; SIEMENS IS IN TALKS TO BUY PYRAMID TECHNOLOGY], Published: January 10, 1995, The New York Times Company</ref><ref>[https://www.nytimes.com/1995/01/24/business/company-news-siemens-agrees-to-purchase-pyramid-technology.html COMPANY NEWS; SIEMENS AGREES TO PURCHASE PYRAMID TECHNOLOGY], Published: January 24, 1995, The New York Times Company</ref><ref>[https://books.google.com/books?id=rmDfSIoLBLMC&dq=SIEMENS+BUYs+PYRAMID+TECHNOLOGY&pg=PT29 Siemens/Pyramid seek to raise profile], By Michael Goldberg, Computerworld, 12 Feb 1996, ''The acquisition last March''</ref> In 1998 this unit was split, with the services side of the operation becoming [[Wincor Nixdorf]]. In 1999 Siemens and [[Fujitsu]] merged their computer operations to form [[Fujitsu Siemens Computers]], and finally [[Amdahl Corporation|Amdahl]] was added to the mix in 2000.

==Products==

===90x===
The first Pyramid Technology series of minicomputers was released in August 1983<ref>[https://books.google.com/books?id=soGti0kvtgwC&dq=Pyramid+90x+computer.&pg=RA1-PA73 Supports Up to 128 Users Pyramid 32-Bit Mini Designed for Unix], Page 73, Computerworld, 15 Aug 1983, ''...has unwrapped a 32-bit, ...minicomputer...Pyramid 90x...''</ref><ref>[https://books.google.com/books?id=_itgx7IkelMC&dq=Pyramid+Technology+Corp.%2C+Mountain+View%2C+CA&pg=RA1-PA184 Position advert: Pyramid Systems Support Specialist], Page 184, Computerworld, 12 Sep 1983, ''Pyramid Technology Corporation, a new Mountain View, California company focused on ... has recently announced its first product: the Pyramid 90x computer.''</ref> as the 90x superminicomputer, which used their custom [[32-bit]] scalar processor running at 8&nbsp;MHz.

Although the architecture was marketed as a [[RISC]] machine, it was actually [[microcode|microprogrammed]]. It used a "sliding window" register model based on the [[Berkeley RISC]] processor, but memory access instructions had complex operation modes that could require many cycles to run. Many register-to-register scalar instructions were executed in a single machine cycle. Initially, floating point instructions were executed totally in microcode, although an optional floating point unit on a separate circuit board was released later. Microprogramming also allowed other non-RISC luxuries such as block move instructions.

Programs had access to 64 registers, and many instructions were triadic. Sixteen registers (registers 48 to 63) were referred to as "global registers" and they correspond to the registers of a typical CPU, in that they are static and always visible. The other 48 registers were actually the top of the subroutine stack. Thirty-two of them (0–31) were local registers for the current subroutine, and registers 32–47 were used to pass up to 16 parameters to the next subroutine called. During a subroutine call, the register stack moved up 32 words, so the caller's registers 32–47 became the called subroutine's registers 0–15. The return instruction dropped the stack by 32 words so return parameters would be visible to the caller in registers 32–47. The stack cache held 16 levels in the CPU and stack overflow and underflow was automatically handled by the microcode of the CPU. The programming model had two stacks, one for the register stack, and one for subroutine local variables. One grew up from a designated address in the middle of the address space, and the other grew down from the top of the user mode address space.

The 90x could accommodate four memory boards, initially holding 1&nbsp;MB each. This was considered to be a lot of memory at the time, but the RISC-like architecture resulted in bigger programs than earlier architectures so most machines were sold with the memory slots full. Fortunately, the 1&nbsp;MB memory boards had RAM in sockets, so they could be upgraded to 4&nbsp;MB units when bigger dynamic RAM devices became available shortly after the 90x's initial release.

The 90x competed with the [[Digital Equipment Corporation]] (DEC) [[VAX]] 11/780 which was the preferred platform for running UNIX in the early 1980s. The 90x processor benchmarked at roughly twice the speed of the VAX, and sold for about half the price. Pyramid was indirectly assisted by DEC's reluctance to sell VAX machines without the [[OpenVMS|VMS]] operating system, for which they charged a considerable amount of money. Many universities wanted to run UNIX rather than VMS, so Pyramid's higher performance and lower price, coupled with artificial delivery delays or surcharges from DEC, helped them to make the risky decision to buy from a new manufacturer.

One of the 90x's biggest advantages over the competition was its asynchronous serial port controller (the ITS or Intelligent Terminal Server) based on a 16-bit bit-slice processor. The ITS interfaced to 16 serial ports, and it could run them at very high speeds, using DMA to feed from daisy-chained output data blocks. A machine could have many ITSs installed, each one with its own I/O processor. Other machines at the time (including the 11/780) required CPU intervention every few bytes for interactive users, which added significantly to the system component of the CPU load. As a result, the 90x scored very well on benchmarks with a realistic amount of serial I/O.

The disk and magnetic tape controllers were actually 16-bit third-party [[Multibus]] controllers fitted into a socket in a U-shaped bus-adapter board.

Most early systems were delivered with the 470&nbsp;MB [[Fujitsu Eagle]] disk drive and a slot-loading reel-to-reel streaming tape drive.

Just like the VAX 11/780, which had a [[PDP-11|PDP-11/03]] with a ((convert|8|in|adj=on)) floppy disk as its console processor, the 90x had a "System Support Processor", based on a [[Motorola 68000]], that loaded the microcode from an ((convert|5.25|in|adj=on)) floppy disk when the system was started. It was also able to run a suite of diagnostics over the system. It had a [[modem]] which allowed remote analysis by the manufacturer. The software run by the administrative processor was initially called the Totally Unrealistic Remote Diagnostic. This name was changed some years later.

A minimal system was delivered in a single ((convert|19|in|adj=on)) rack about ((convert|60|in|adj=on)) high with the card cage in the bottom, the disk drive in the middle, the tape drive above it, then the 2 inch high control panel with a floppy disk drive and ignition key on the top. This was considered very compact at the time. At least one machine in Australia spend six months installed in a retired outdoor lavatory with an air-conditioner replacing the louvered window and the system console terminal sitting on top of the cabinet. Administration tasks were performed al-fresco. The only indicator on the control panel was an 8 segment bar graph LED display that displayed average CPU usage when the machine was running and a "[[Cylon (Battlestar Galactica)|Cylon]] Eye" pattern when the machine stopped unexpectedly. The machine was low enough that the console (a monochrome asynchronous terminal) could rest on top.

===98x===
The 90x was fairly quickly followed by the 98x which was identical except that the processor clock speed was increased to 10 MHz.

Initially a single processor system like its predecessor, the 98x became Pyramid's first [[symmetric multiprocessing|SMP]] in 1986. Several machines in the series were released, from the 1-CPU 9805 to the 4-CPU 9845, over a period of years from 1985 to 1987. The fully loaded 9845 ran at about 25&nbsp;[[million instructions per second|MIPS]], a respectable figure for the era, though not competitive with high-end [[supercomputer]]s.

Addressing the growing but cost sensitive workstation sever market, Pyramid introduced the '''WorkCenter''' in 1986, essentially a half-height, lower cost version of the 98x with a horizontally mounted 9-track tape drive and ((convert|8|in|adj=on)) disk drive(s).<ref>((Cite book |last=Enterprise |first=I. D. G. |url=https://books.google.com/books?id=POjXwPy5eBUC&dq=pyramid+technology+workcenter&pg=PA25 |title=Computerworld |date=1986-02-17 |publisher=IDG Enterprise |language=en))</ref>

All early Pyramid 9xxx systems - from the 90x to the 9810 - used the same physical bus and were field upgradeable.<ref>((Cite web |title=Pyramid 9810 brochure (pdf) |url=https://archive.computerhistory.org/resources/access/text/2015/07/102664506-05-01-acc.pdf |access-date=15 January 2022 |website=Computer History Archive))</ref>

===MIServer===
Like many of the early multiprocessor vendors, Pyramid turned to "commodity" RISC CPUs when they started to become practical. Pyramid continued to use their own RISC design until the release of the MIServer S product line. Pyramid released a series of register window-based machines as a 9000 line follow on. These were known as the MIServer starting in 1989. They supported up to ten CPUs with performance of about 12&nbsp;MIPS each. The MIServer was replaced in 1991/2 with the MIServerT and later followed up with the MIServer S and ES, Pyramid's first [[R3000]]-based machine. The first machines in the series shipped with anywhere from 4 to 12 R3000s running at 33&nbsp;MHz, with top-end performance around 140&nbsp;MIPS. Later high-end MIServer ES machines had up to 24 CPUs, also at 33&nbsp;MHz. The operating system for the MIPS based systems was [[DC/OSx]], a port of [[AT&T Corporation|AT&T]] [[UNIX System V|System V Release 4]] (SVR4).

===Nile series===
The release of the 150&nbsp;MHz 64-bit [[R4000|R4400]] led to the 2–16-CPU Nile series in late 1993. With each CPU capable of 92&nbsp;MIPS, the Nile systems were true supercomputers. Their last product, the Reliant RM&nbsp;1000, known internally as the Meshine, was just coming to market when Siemens bought them. The RM1000 was a [[massive parallel processing]] (MPP) computer. Each node ran its own instance of [[Reliant UNIX]] DC/OSx. This system had a two-axis mesh architecture. The RM1000 used software called ICF to manage the cluster interconnects. ICF went on to provide the cluster foundation in the [[PrimeCluster HA]] software which is still developed and available from Fujitsu Siemens.

Each compute node in the mesh used a single MIPS [[R10000]] CPU, however enhancements to the RM1000 allowed for the NILE SMP machines to be included into the mesh as "fat" nodes. The compute nodes were physically installed in the [[HAAS-3]] frames that shipped as drive arrays with the earlier Nile product. Each compute node controlled six SCSI disks as the primary controller and another six disks as a secondary controller. The frame with up to six compute nodes or four compute nodes and two Nile attach gateways was connected to neighboring frames with short ribbon cables. A HAAS-3 frame with compute nodes installed was called a cell. The cells locked together and could be stacked two high and end to end as far as space permitted. Four cells together were known as a ton and systems were referred to by the number of tons they contained. The largest mesh constructed at Pyramid was a test system containing 214 CPUs including four Nile SMP nodes.

Although the RM1000 was eventually discontinued and not replaced by Siemens, customers who had large installations such as a large UK telecommunications company took a long time to find suitable replacements for these massively parallel systems due to their massive I/O and computing capabilities.

==References==
((reflist))

== External links ==
* [http://edgar.secdatabase.com/2781/89161894000268/filing-main.htm Pyramid Technology, Form 10-K, Annual Report, Filing Date Dec 22, 1994]

[[Category:Defunct semiconductor companies of the United States]]
[[Category:Technology companies based in the San Francisco Bay Area]]
[[Category:Defunct companies based in the San Francisco Bay Area]]
[[Category:Computer companies established in 1981]]
[[Category:Manufacturing companies established in 1981]]
[[Category:Manufacturing companies disestablished in 1995]]
[[Category:1981 establishments in California]]
[[Category:1995 disestablishments in California]]
[[Category:Defunct computer hardware companies]]
[[Category:Defunct computer systems companies]]
[[Category:Defunct computer companies of the United States]]

Pages transcluded onto the current version of this page (help):

Pyramid Technology (edit)
Template:Ambox (view source) (template editor protected)
Template:Cite book (view source) (protected)
Template:Cite web (view source) (protected)
Template:Convert (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Refimprove (view source) (template editor protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Convert (view source) (template editor protected)
Module:Convert/data (view source) (template editor protected)
Module:Convert/text (view source) (template editor protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to Pyramid Technology.

Retrieved from "https://en.wikipedia.org/wiki/Pyramid_Technology"