Hubbry Logo
Sun4dSun4dMain
Open search
Sun4d
Community hub
Sun4d
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Sun4d
Sun4d
Sun4d
View on Wikipedia
from Wikipedia
SPARCserver 1000 and SPARCstorage Array

Sun4d is a computer architecture introduced by Sun Microsystems in 1992. It is a development of the earlier Sun-4 architecture, using the XDBus system bus, SuperSPARC processors, and SBus I/O cards. The XDBus was the result of a collaboration between Sun and Xerox; its name comes from an earlier Xerox project, the Xerox Dragon. These were Sun's largest machines to date, and their first attempt at making a mainframe-class server.

Architecture

[edit]

Sun4d computers are true SMP systems; although memory and CPUs are installed per system board, the memory on a given board is not in any way "closer" to the CPUs on that same board. All memory and I/O devices are equally connected to all CPUs.

All of these computers use a passive backplane into which system boards are plugged. Each system board provides CPUs, memory, and an I/O bus. As system boards are added, these components are added to the whole in a completely seamless fashion. It is not a cluster, but works as a single large machine.

Machines

[edit]

Sun4d computers include the SPARCcenter 2000 (1992) and SPARCserver 1000 (1993) from Sun Microsystems, and the Cray CS6400 (1993) from Cray Research. The system boards in these three machines are all slightly different, physically and electronically, and are not interchangeable.

All Sun4d machines provide JTAG ports, although unlike later systems the SPARCcenter and SPARCserver only use it for maintenance purposes.

SPARCserver 1000

[edit]
SS1000E
SS1000E System Board

The SPARCserver 1000 is a 5U rackmountable chassis with four 40 MHz XDBus slots, and space for four half-height 3.5" SCSI drives plus two half-height front-accessible 5.25" SCSI drives (typically used for CD-ROM and DAT). Each system board connects to one XDBus and provides two MBus slots for CPUs, three SBus slots for I/O boards, four banks of memory (four SIMMs apiece), and builtin SCSI-2, 10baseT Ethernet, and two serial ports.[1]

Maximum configuration: eight CPUs and 2 GB RAM.

The SPARCserver 1000E has a slightly faster XDBus (50 MHz). The system boards are not backwards compatible.

The SPARCserver 1000, like earlier Sun-4/xxx servers, has a set of LEDs on each system board that display diagnostics on POST, and CPU load while running. These allow the user to see at a glance how busy each processor on the system is. They are informally referred to as "Cylon" displays, because of the way each displays a single light bouncing back and forth resembles the scanner of the robots in the original Battlestar Galactica television series.[2]

The SPARCserver 1000 will run a slightly-patched Linux 2.4 kernel in SMP mode. [3]

A single octo-processor SPARCserver 1000 helped 117 SPARCstation 20 Model HS11 units, 87 with two 100 MHz hyperSPARC processors and 30 with four 100 MHz hyperSPARC processors, to render Toy Story.[4]

SPARCcenter 2000

[edit]

The SPARCcenter 2000 is a full rack system that includes a main chassis with ten 40MHz dual-XDBus slots and several disk arrays. The system boards connect to two XDBuses for extra bandwidth, and provide two MBus slots, four SBus slots, four banks of memory (four SIMMs apiece), and two serial ports apiece. Unlike the SPARCserver 1000 boards, they do not have a builtin SCSI and Ethernet port per system board.[5]

Maximum configuration: twenty CPUs and 5 GB RAM.

The SPARCcenter 2000E has a slightly faster XDBus (50 MHz). The system boards are not backwards compatible.

Cray Superserver 6400

[edit]

The Cray CS6400 is a 16-slot, 55 MHz quad-XDBus system. Each system board provides four MBus slots, four SBus slots, four banks of memory, and no builtin I/O ports.

Maximum configuration: sixty-four CPUs and 16 GB RAM.[6]

When SGI purchased Cray Research in 1996, they sold the division responsible for the CS6400 to Sun, where it was developed into the extremely successful Sun Enterprise 10000.[7]

Performance

[edit]

Relative performance of Sun-4d machines, based on SPEC CINT92 Rate benchmarks:[8][9]

System Processors geometric mean rate_int92 008 espresso SPEC rate 022 li SPEC rate 023 eqntott SPEC rate 026 compress SPEC rate 072 sc SPEC rate 085 gcc SPEC rate
CS6400 64 101969 98449 147287 139144 32849 214882 78932
SC2000E 20 53714 46817 54551 74541 28564 107441 41111
SS1000E 8 21758 19578 26184 26089 11680 45238 15014

References

[edit]
[edit]

See also

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Sun4d

View on Grokipedia
from Grokipedia
The Sun4d is a 32-bit introduced by in 1992 as an evolution of the earlier architecture, specifically designed for scalable, mainframe-class multiprocessing servers using the instruction set and featuring the XDBus for interconnectivity. Developed in collaboration with , it utilized SuperSPARC processors alongside MBus and interfaces to enable environments. Key systems based on the Sun4d architecture include the SPARCserver 1000, SPARCcenter 2000, and Superserver 6400, designed to handle demanding enterprise workloads. Unlike the contemporaneous Sun4m architecture, which relied solely on MBus and for 32-bit operations, Sun4d incorporated the XDBus for enhanced distributed processing capabilities, while differing from the later 64-bit Sun4u architecture that scaled to up to 64 CPUs via the UPA interconnect. This design marked ' initial foray into large-scale server systems, emphasizing modularity and performance for commercial and industrial applications. Support for Sun4d-based hardware was provided through the Solaris operating system up to version 8, after which these systems were deprecated in favor of newer architectures, with hardware options dependent on Sun4d potentially losing compatibility in subsequent releases. Today, emulation and solutions allow legacy Sun4d systems to run on modern hardware, preserving access to historical environments.

Introduction and History

Overview

Sun4d is a (SMP) architecture developed by and introduced in 1992 for enterprise server applications. It enables scalable, shared-memory computing using processors, targeting high-availability business workloads that require mainframe-class performance and reliability. A core purpose of Sun4d was to provide modular expansion for demanding enterprise environments, supporting and high I/O throughput to handle complex applications such as database management and . Key innovations include the XDBus, a packet-switched for efficient inter-processor communication and data sharing across nodes, and a passive design that enhances by allowing hot-pluggable system boards without active signal regeneration. Sun4d evolved from the earlier architecture by incorporating access mechanisms and improved I/O capabilities through the interface, addressing limitations in and bandwidth of prior designs. Basic specifications include support for up to 64 processors in top configurations, such as the Superserver 6400, along with scalable memory up to 16 GB and JTAG-based maintenance ports for diagnostics and boundary scanning.

Development and Release

The Sun4d architecture emerged in the early as ' strategic extension of its line, addressing the increasing demand for high-performance, scalable multiprocessor servers suitable for enterprise environments beyond the desktop and workstation focus of prior systems. This development reflected broader industry trends toward shared-memory multiprocessing for demanding applications, building on processor technology to enable systems with up to 20 processors. Key milestones in Sun4d's creation included initial internal drafts dating back to January 1990, with the first general release of the architecture document in March 1990, followed by progressive revisions incorporating features like those from the project. The formal architecture specification was finalized and released in June 1992 as Revision 1.4, renaming it the Sun-4D Architecture and aligning it with standards for kernel and diagnostic programming. The first hardware implementation, the SPARCcenter 2000, was announced in November 1992, with initial shipments beginning late that year to support first customer ship (FCS) systems. Sun4d's development involved significant partnerships to accelerate scalability and expertise in large-scale systems. A key collaboration was with , evident in joint copyright holdings from 1989 to 1992 and shared "Sun/Xerox Private Data" markings on core documents, which contributed to the derived from Xerox's project. Additionally, in January 1992, entered a technology agreement with Research to co-develop high-end -based superservers in the $1 million to $3 million range, leveraging Cray's multiprocessing knowledge; this partnership culminated in the Cray Superserver 6400, released in 1993 as a Sun4d-compatible system supporting up to 64 processors. The architecture was publicly positioned for enterprise markets, directly competing with established players like and DEC in sectors requiring robust computing power, such as database management and network services. Sun4d systems, including the SPARCcenter 2000 and subsequent SPARCserver 1000 (shipped starting in 1993), marking Sun's entry into mainframe-class territory.

Technical Architecture

System Design and Components

The Sun4d architecture employs a passive design that interconnects multiple system boards, each capable of housing processors, memory modules, and I/O interfaces, to enable scalable (SMP) configurations. This modular approach allows for the independent addition or removal of components, facilitating expansion without requiring a complete system redesign. The passive itself contains no active logic, relying instead on the system boards to handle processing and control functions, which promotes reliability through simplified interconnects and easier fault isolation. In Sun4d systems, SMP is implemented with uniform access to and I/O resources across all processors, ensuring no locality bias where memory on one board is preferentially closer to its local CPUs. This symmetric design supports configurations ranging from a few processors to up to 64-way SMP in extended implementations, such as those derived from the Superserver 6400, by distributing workloads evenly via cache consistency protocols like write-back and write-broadcast mechanisms. Component is further enhanced by standard slots—typically four per I/O unit—for expandable peripherals like controllers and Ethernet adapters, alongside ports that enable boundary-scan testing, firmware updates, and diagnostics during initialization and maintenance. Reliability is a core aspect of the design, incorporating as standard to detect and correct single-bit errors while identifying multi-bit faults, thereby minimizing in high-availability environments. Redundant power supplies are integrated to provide capability, with system monitoring for AC/DC failures ensuring continuous operation. This marks a significant from the earlier architecture, which relied on a monolithic limiting scalability; Sun4d's shift to distributed system boards plugged into the allows for greater expansion and easier upgrades, accommodating larger SMP clusters without the constraints of a single-board layout.

Bus System and Scalability

The XDBus is a , scalable system bus developed jointly by and PARC for high-performance multiprocessor environments in Sun4d architecture. It serves as the primary interconnect for CPU-to-memory access and inter-processor communication, enabling (SMP) configurations. Operating at a clock frequency of 40 MHz, the XDBus features a 64-bit multiplexed /data path with additional parity bits for , utilizing low-voltage Gunning Transceiver Logic (GTL) signaling to support long bus lengths and low power consumption. Sun4d systems employ a hierarchical XDBus to achieve , where individual system boards connect to one or more bus segments, allowing incremental addition of processing and memory resources. In base configurations like the SPARCserver 1000, a single XDBus supports up to four system boards and eight SuperSPARC processors, with each board providing two MBus slots for CPUs and memory banks. Larger setups, such as the SPARCcenter 2000, utilize dual XDBuses per board across multiple backplanes, scaling to 20 processors while maintaining consistent cache coherency through the (Modified, Owned, Exclusive, Shared, Invalid) protocol. In extended implementations like the Superserver 6400, up to four XDBuses interconnect to support as many as 64 processors, though this requires domain partitioning for management. The XDBus delivers a peak throughput of 320 MB/s per bus segment, calculated from its 64-bit width and 40 MHz operation, with pipelined packet-switched transactions (2- or 9-cycle packets) to sustain high utilization in SMP workloads. Fair access in multi-processor environments is ensured by a two-tier mechanism: board-level arbiters (BARB) prioritize local requests, while a central arbiter (CARB) on the control board resolves inter-board contention, minimizing latency for operations. This design contrasts with the , a 32-bit peripheral I/O bus running at 25 MHz (limited to about 100 MB/s peak), which handles only device expansion and lacks the XDBus's support for scalable coherence and system-level traffic. Despite its scalability, the XDBus topology imposes limitations, as systems rely on fixed interconnections that demand balanced population of CPU and slots to avoid bottlenecks in uneven configurations. Optimal requires careful of board placement to maximize interleave , such as 64-byte striping within segments or 256-byte across dual buses, preventing contention in high-load scenarios.

Processor and Memory Subsystems

The Sun4d processor subsystem centers on the SuperSPARC (also known as Viking) CPU, a V8-compliant implementation featuring an integrated integer unit, , and SPARC Reference MMU, with internal caches of 20 KB for instructions and 16 KB for data. These processors operate at clock speeds of 40 to 60 MHz, depending on the module variant, and include an external L2 cache of 1 MB (with support for a degraded 512 KB mode) that is direct-mapped, write-back, and physically addressed in 256-byte blocks for both instructions and data. The cache controller manages consistency via write-broadcast protocols, and each CPU module may contain one or two processor sets sharing resources like the external cache. CPU boards in Sun4d systems are designed to hold 1 or 2 SuperSPARC processors across two MBus slots, where each slot accommodates a module with one CPU, along with integrated cache controllers. These boards connect the processors to the XDBus for shared access to and I/O, enabling configurations while supporting mode for standalone operation with local and peripherals. Power delivery occurs via per-board to handle the multi-CPU density, with forced-air cooling systems ensuring thermal management through monitored fans and temperature sensors that trigger interrupts on failures. The memory subsystem utilizes distributed DRAM SIMMs with error-correcting code (ECC) protection, implementing SEC-DED-S4ED to correct single-bit errors and detect up to quadruple-bit errors, with logging and interrupt handling for both correctable and uncorrectable faults. Each board supports up to 2 GB of main memory in four banks (16 SIMM slots total, installed in groups of four), using densities from 4 Mbit to 16 Mbit chips for capacities ranging from 32 MB minimum, depending on SIMM density. Memory is organized with two banks per board in multi-Dynabus configurations (e.g., SunDragon setups), and the Memory Queue Handler ASIC manages access, including non-volatile SRAM mirroring for boot purposes. Interleaving occurs across banks and buses—up to 4-way for performance—aligning on 64-byte increments within a Dynabus or 256-byte boundaries across multiple buses to balance load and reduce contention.

Hardware Implementations

SPARCserver 1000

The SPARCserver 1000, introduced by in May 1993 as an entry-level implementation of the Sun4d architecture, served as a compact multiprocessor server targeted at departmental environments. It featured a 5U rackmount form factor with dimensions of approximately 8.3 inches in height, 20 inches in width, and 21 inches in depth, allowing for stackable or rack-mounted deployment in space-constrained settings. Weighing around 70 pounds depending on configuration, the system emphasized reliability through its integrated design, including a 650-watt supporting 100-240 VAC input and a side-mounted fan tray for airflow management. Configuration options for the SPARCserver 1000 centered on scalability within a four-system-board , supporting 1 to 8 SuperSPARC processor modules operating at 40 MHz, with two modules per board. capacity reached up to 2 GB using 32 MB SIMMs installed in groups of four across 16 slots, while expansion included up to 12 slots at 20 MHz (three per board) for I/O adapters. Base models typically shipped with four SuperSPARC CPUs, 128 MB of RAM, and 2 GB of , alongside onboard SCSI-2 interfaces and twisted-pair Ethernet per board; internal storage supported up to 16.8 GB, with optional tape drives and . Unique to the SPARCserver 1000 was its compact architecture optimized for mid-range enterprise applications, such as and teleservices, featuring fault-resilient elements like redundant cooling via a fan tray with failure sensors and hot-swappable power options. The design incorporated an optional NVRAM module for NFS acceleration, enhancing performance in networked environments. Initial pricing began at $36,700 for a uniprocessor configuration with 32 MB RAM and 1 GB disk, scaling to $75,700 for the four-processor base model and up to $110,000 for fully loaded systems, positioning it as an accessible option for organizations needing up to 350 transactions per second. Maintenance was facilitated by front-accessible component bays, enabling easy replacement of boards, SIMMs, and drives without full system disassembly, complemented by built-in diagnostics via interfaces for troubleshooting processor and bus issues. This approach, combined with a one-year on-site warranty, supported reliable deployment in enterprise settings.

SPARCcenter 2000

The SPARCcenter 2000, introduced by in 1992, served as a mid-range scalable server designed for enterprise environments requiring robust capabilities. It featured a full rackmount form factor, measuring approximately 56 inches in height to accommodate extensive internal components within a standard 19-inch wide chassis, enabling deployment in data centers for high-availability operations. This system marked a step up from entry-level models by emphasizing domain partitioning for enhanced reliability in mid-scale setups. Configurations of the SPARCcenter 2000 typically supported 8 to 20 CPU slots across up to 10 system boards, each capable of holding two SuperSPARC processor modules with mixed speeds such as 40 MHz, 50 MHz, or 60 MHz. capacity ranged from 64 MB to a maximum of 5 GB, utilizing high-density boards with 8 MB or 32 MB DRAM modules and 1 MB NVSIMMs for non-volatile storage, protected by ECC and with memory interleaving across boards and XDBuses for improved bandwidth. The system included 8 slots in base configurations, expandable to 40 across all boards, facilitating integration of I/O peripherals while maintaining up to 640 MB/s aggregate bandwidth via the XDBus interconnect. A key unique feature was its dual-domain , achieved through twin independent XDBuses that divided the system into two fault-isolated halves, allowing automatic reconfiguration to bypass failed components such as processors or units without full system . This design provided high-density integration and JTAG-based diagnostics for rapid fault isolation, ensuring continued operation even if one domain experienced issues, with reducing bandwidth but preserving functionality. In contrast to smaller, non-partitioned entry-level servers, the SPARCcenter 2000's rack-oriented with domain support targeted mid-scale deployments needing resilient partitioning. The SPARCcenter 2000 was optimized for database servers and (OLTP) workloads in large enterprises, supporting over 1,000 concurrent users in fully configured setups for applications like management systems (RDBMS) and client-server computing. Its modular construction allowed field upgrades to the full 20-CPU capacity, with provisions for adding system boards and memory without major . Optional fiber-optic extensions for the XDBus enabled inter-cabinet connectivity in clustered environments, further enhancing scalability for distributed enterprise tasks.

Cray Superserver 6400

The Cray Superserver 6400 (CS6400) emerged from a 1992 technology agreement between Cray Research and , establishing Cray Research Superservers, Inc. (CRS) as the entity to develop and market high-end SPARC-based systems compatible with Sun's architecture. Announced on October 25, 1993, this air-cooled superserver represented a joint engineering effort to extend Sun4d scalability for enterprise environments, with initial shipments occurring late that year and volume production ramping up in the first quarter of 1994. Housed across multiple cabinets to accommodate its expansive design, the CS6400 targeted organizations requiring robust, multi-processor computing beyond standard Sun offerings. The system supported configurations ranging from 4 to 64 SuperSPARC processors, operating at 60 MHz initially and later upgradable to 85 MHz SuperSPARC-II modules, distributed across four independent domains for enhanced parallelism. Each domain provided up to 16 CPU slots, enabling a maximum of 64-way (SMP), paired with up to 16 GB of RAM and 16 slots per domain for I/O expansion. This modular setup allowed incremental scaling, with base systems starting at 4 processors and 256 MB RAM, while fully loaded variants reached 64 processors and 16 GB, supporting up to 5 TB of online storage through extensive I/O capabilities. Distinctive features included a Quad-XDBus crossbar interconnect operating at 55 MHz across four buses, delivering 1.76 GB/s aggregate bandwidth to minimize memory contention in 64-way SMP operations. Drawing on Cray's expertise, the design incorporated advanced thermal management via software-controlled chassis fans and custom CPU modules to prevent overheating in dense configurations, alongside reliability enhancements such as hot-swappable components, automatic reboot mechanisms, fault isolation, , and . A dedicated System Service Processor (SSP) monitored hardware and facilitated rapid recovery, ensuring for mission-critical workloads. Primarily aimed at applications, the CS6400 excelled in complex simulations, large-scale database processing, decision support systems, data warehousing, , and multimedia tasks. It integrated seamlessly with off-the-shelf Solaris applications, including Oracle7 and Online Dynamic Server, serving sectors like , , , and where scalable SMP performance was essential. Manufactured exclusively by CRS in facilities supporting Cray's high-reliability standards, the CS6400 saw limited production and sales, with notable deployments including a 48-processor system for in and a 16-processor unit (upgradable to 32) for in applications. Pricing ranged from $400,000 for entry-level models to $2.5–4 million for maximum configurations, reflecting its specialized nature; support effectively ended around 1997 following Sun's 1996 acquisition of the CRS business unit.

Software Support

Operating Systems

The Sun4d architecture primarily supported Sun Microsystems' proprietary operating systems, beginning with 4.1.4, which provided initial compatibility for systems like the SPARCserver 1000 and SPARCcenter 2000 through kernel patches enabling multiprocessor operation. This version, released in 1994, included (SMP) extensions via MP patches that allowed multiple SuperSPARC processors to share workloads, though performance was limited compared to later releases due to the architecture's NUMA () design. Installation on 4.1.4 typically involved PROM-based from the OpenBoot firmware, which handled diagnostics and initialization, with support for NFS root mounts and network-based installations over Ethernet for diskless configurations. By 1993, support transitioned to Solaris 2.x (internally SunOS 5.x), starting with Solaris 2.2, which offered native compatibility and enhanced kernel features for Sun4d hardware. Solaris 2.3 and subsequent versions introduced full SMP support, including NUMA-aware scheduling that optimized thread placement across nodes connected via the XDBus, reducing latency in multi-processor setups. processes remained PROM-driven with OpenBoot for hardware verification and error reporting, while installation options expanded to include , tape, and network jumps via for automated deployment in enterprise environments. Solaris versions up to 2.6 (released in 1997) provided the last major optimizations tailored for Sun4d, such as improved I/O handling and scalability patches for up to eight processors, after which focus shifted to newer architectures like sun4u. Beyond Solaris 8 (2000), Sun4d support was deprecated in favor of 64-bit platforms. Third-party operating system support was limited, with distributions offering partial compatibility starting around 2001. 2.4 provided SMP-capable operation on SPARCserver 1000 models through community-patched versions, enabling basic but lacking full NUMA optimizations found in kernels; this support was experimental and primarily used for legacy testing rather than production workloads.

Compatibility and Features

The Sun4d architecture ensured full binary compatibility with applications compiled for earlier and Sun-4c systems, as all adhered to the V8 , enabling most binaries to execute without recompilation on Sun4d platforms running Solaris. This compatibility extended across Solaris releases, allowing seamless migration of software from sun4c and sun4m environments to sun4d servers in networked setups, such as diskless clients. Key features of the Solaris operating system on Sun4d included support for clustering via Sun Cluster 1.0, introduced in 1996 as an evolution of the 1995 Solaris Multicomputer project, which enabled high-availability configurations for enterprise workloads. Additionally, it incorporated NIS+ for distributed network information services and RPC mechanisms for remote procedure calls, facilitating scalable networked environments in multi-node setups. Application support on Sun4d was optimized for database systems through Sun's partnerships with and Sybase, which provided certified drivers and for Solaris platforms in the mid-1990s. The also included the Java runtime environment from JDK 1.0.2, released in 1996, allowing cross-platform development and deployment of applications on Sun4d servers without architectural modifications. A notable limitation was the absence of 64-bit addressing support until Solaris 7 in 1998, which was restricted to UltraSPARC (sun4u) platforms, thereby capping Sun4d systems at 32-bit memory addressing and hindering large-scale memory utilization for memory-intensive applications.

Performance and Legacy

Benchmarks and Metrics

Sun4d systems were evaluated using the SPEC CPU92 benchmark suite, which measures compute-intensive performance through (CINT92) and floating-point (CFP92) workloads. SPECrate_int92 and SPECrate_fp92 metrics, representing throughput on multiprocessor configurations, demonstrated with increasing CPU counts. Representative results from standardized tests highlight the architecture's capabilities in balanced and floating-point tasks.
System ConfigurationSPECrate_int92SPECrate_fp92Source
SPARCserver 1000E (8 CPUs, 85 MHz SuperSPARC)21,75820,851Tech Monitor (1995)
SPARCcenter 2000E (20 CPUs, 85 MHz SuperSPARC-II)57,99754,206Tech Monitor (1995)
Cray Superserver 6400 (64 CPUs, 60 MHz SuperSPARC)101,969129,843Netlib PDS (1995); Cray CS6400 Brochure (1995)
These scores reflect peak configurations under controlled conditions, with geometric means calculated across six integer and fourteen floating-point benchmarks. In transaction processing, Sun4d systems supported OLTP workloads via early TPC benchmarks like TPC-B, achieving up to over 2,000 tpmB in high-end Superserver 6400 setups with configurations. For high-performance computing, on Sun4d platforms delivered multi-GFLOPS performance suitable for scientific simulations, with the Superserver 6400 rated at up to 3.8 GFLOPS in base modules scaling with processor additions. Benchmark results from 1993 to 1995, primarily conducted in laboratories, showed variability depending on CPU count and memory interleaving across XDBus slots. Performance scaled near-linearly up to 20 processors but exhibited 2-4x improvements over prior MP systems in multi-threaded tasks due to enhanced bus design. In high-CPU configurations exceeding 20 processors, bus contention increased, reducing efficiency as multiple processors competed for shared resources on the XDBus.

Impact and Successors

The Sun4d architecture significantly contributed to ' growth in the enterprise server market during the early , with server sales driving overall revenue expansion to $5.9 billion in fiscal 1995. These systems were used in enterprise environments for high-availability computing, supporting early networked applications. Despite its strengths, Sun4d faced notable limitations, particularly in cost and scalability. Fully configured systems like the Superserver 6400 could exceed $1 million, restricting adoption to large enterprises. Additionally, the architecture's maximum of 64 CPUs in models such as the CS6400 created bottlenecks for further expansion, contributing to a market decline by the mid- as demand shifted toward more scalable designs. Sun4d paved the way for successors like the Sun Enterprise series under the Sun4u architecture. In 1995, Sun acquired Cray's server business, adapting the CS6400 design for the Sun Enterprise 10000, introduced in 1997 with UltraSPARC processors to address and improved interconnects. This transition influenced subsequent networking advancements, including integrations with emerging standards for enhanced server performance. The legacy of Sun4d bolstered SPARC's dominance in enterprise environments through the 1990s and into the early 2000s, enabling Sun to capture significant from proprietary competitors via standardized RISC architectures. Today, preservation efforts include emulation through tools like , which supports platforms to run legacy Sun4d-compatible software on modern hardware. Oracle discontinued support for Sun4d hardware in Solaris 9 (released in 2002), with no further patches issued after the 2010 acquisition of Sun, marking the end of official maintenance.

References

  1. https://www.stromasys.com/resources/understanding-sun4u-sun4m-and-sun4d/
  2. https://docs.oracle.com/cd/E19455-01/806-5189/eos-31/index.html
  3. https://cray-history.net/wp-content/uploads/2021/08/Cray_Superserver-CS6400-brochure_redux.pdf
  4. http://www.bitsavers.org/pdf/sun/sparc/Sun4D_Architecture_Jun1992.pdf
  5. http://www.bitsavers.org/pdf/xerox/parc/techReports/CSL-93-17_Papers_from_the_SunDragon_Project.pdf
  6. https://www.nytimes.com/1992/01/23/business/cray-in-pact-to-use-chip-made-by-sun.html
  7. https://cray-history.net/cray-history-front/fom-home/fom-sparcsuperservers/
  8. https://cray-history.net/2023/12/18/how-the-sun-enterprise-10000-was-born-from-the-cray-cs6400/
  9. https://websrv.cecs.uci.edu/~papers/mpr/MPR/ARTICLES/070301.pdf
  10. https://docs.oracle.com/cd/E19095-01/sparc1k.srvr/801-2895-15/801-2895-15.pdf
  11. https://ieeexplore.ieee.org/document/289692
  12. https://www.dcs.ed.ac.uk/home/rah/Resources/Sun/SunPerfOvDec93.pdf
  13. https://docs.oracle.com/cd/E19957-01/801-2035-12/chap1.html
  14. https://docs.oracle.com/cd/E19620-01/805-4448/z40000283853/index.html
  15. https://www.techmonitor.ai/technology/sun_sparcserver_1000_fills_500_and_3000_user_gap
  16. https://docs.oracle.com/cd/E19620-01/805-4448/z40000283874/index.html
  17. https://docs.oracle.com/cd/E19095-01/ctr2k.srvr/801-2007-18/801-2007-18.pdf
  18. https://www.techmonitor.ai/technology/cray_launches_its_four_to_64_sparc_cs6400_superserver
  19. https://www.filibeto.org/aduritz/supercomputing/cray/cray-cs6400.html
  20. https://www.cpushack.com/CIC/otherpr/cray_6400
  21. https://www.techmonitor.ai/analysis/sgi_sells_crays_sparc_superserver_business_to_sun_evaluates_sale_of_other_units/
  22. http://www.sunhelp.org/pipermail/sunhelp_sunhelp.org/2002-February/015488.html
  23. https://vtda.org/docs/computing/Sun/software/800-6645-10_SunOS4.1.2ReleaseManualRevA_Dec91.pdf
  24. https://docs.oracle.com/cd/E19095-01/sparc1k.srvr/801-2893-13/801-2893-13.pdf
  25. https://shrubbery.net/~heas/sun-feh-2_1/Devices/System_Board/SYSBD_Server_1000.html
  26. https://ptgmedia.pearsoncmg.com/images/0130224960/samplechapter/0130224960.pdf
  27. https://docs.oracle.com/cd/E19455-01/816-1426/eos-31/index.html
  28. https://www.oracle.com/solaris/technologies/solaris9-os-system-requirements.html
  29. https://bugzilla.kernel.org/show_bug.cgi?id=13444
  30. https://docs.oracle.com/cd/E19455-01/806-3771/806-3771.pdf
  31. https://docs.oracle.com/cd/E19620-01/805-6019/805-6019.pdf
  32. https://dokumen.pub/oracle-solaris-cluster-essentials-9780132486224-2010027191-0132486229-1341361381-9780132489409-0132489406.html
  33. https://www.redbooks.ibm.com/redbooks/pdfs/sg246584.pdf
  34. https://landley.net/history/mirror/unix/Solaris_History_6per.pdf
  35. https://docs.oracle.com/cd/E19620-01/805-3727/6j3ht4dp0/index.html
  36. https://cug.org/5-publications/proceedings_attendee_lists/1997CD/F95PROC/61_74.PDF
  37. https://www.encyclopedia.com/economics/economics-magazines/sun-microsystems-inc
  38. https://wiki.debian.org/SunSparc
  39. https://public.dhe.ibm.com/systems/migratetoibm/SPARCfinal.pdf
  40. https://wiki.qemu.org/Documentation/Platforms/SPARC
  41. https://docs.oracle.com/cd/E19683-01/819-3807/eos-31/index.html
Add your contribution
Related Hubs
User Avatar
No comments yet.