List of interface bit rates
Template:SHORTDESC:[[Category:Script error: No such module "pagetype". with short description]]Script error: No such module "Check for unknown parameters".Expression error: Unexpected < operator.Script error: No such module "SDcat". Script error: No such module "Unsubst".
This is a list of interface bit rates, a measure of information transfer rates, or digital bandwidth capacity, at which digital interfaces in a computer or network can communicate over various kinds of buses and channels. The distinction can be arbitrary between a computer bus, often closer in space, and larger telecommunications networks. Many device interfaces or protocols (e.g., SATA, USB, SAS, PCIe) are used both inside many-device boxes, such as a PC, and one-device-boxes, such as a hard drive enclosure. Accordingly, this page lists both the internal ribbon and external communications cable standards together in one sortable table.
Factors limiting actual performance, criteria for real decisions[edit | edit source]
Most of the listed rates are theoretical maximum throughput measures; in practice, the actual effective throughput is almost inevitably lower in proportion to the load from other devices (network/bus contention), physical or temporal distances, and other overhead in data link layer protocols etc. The maximum goodput (for example, the file transfer rate) may be even lower due to higher layer protocol overhead and data packet retransmissions caused by line noise or interference such as crosstalk, or lost packets in congested intermediate network nodes. All protocols lose something, and the more robust ones that deal resiliently with very many failure situations tend to lose more maximum throughput to get higher total long-term rates.
Device interfaces where one bus transfers data via another will be limited to the throughput of the slowest interface, at best. For instance, SATA revision 3.0 (Template:Val) controllers on one PCI Express 2.0 (5 Gbit/s) channel will be limited to the 5 Gbit/s rate and have to employ more channels to get around this problem. Early implementations of new protocols very often have this kind of problem. The physical phenomena on which the device relies (such as spinning platters in a hard drive) will also impose limits; for instance, no spinning platter shipping in 2009 saturates SATA revision 2.0 (3 Gbit/s), so moving from this 3 Gbit/s interface to USB 3.0 at 4.8 Gbit/s for one spinning drive will result in no increase in realized transfer rate.
Contention in a wireless or noisy spectrum, where the physical medium is entirely out of the control of those who specify the protocol, requires measures that also use up throughput. Wireless devices, BPL, and modems may produce a higher line rate or gross bit rate, due to error-correcting codes and other physical layer overhead. It is extremely common for throughput to be far less than half of theoretical maximum, though the more recent technologies (notably BPL) employ preemptive spectrum analysis to avoid this and so have much more potential to reach actual gigabit rates in practice than prior modems.
Another factor reducing throughput is deliberate policy decisions made by Internet service providers that are made for contractual, risk management, aggregation saturation, or marketing reasons. Examples are rate limiting, bandwidth throttling, and the assignment of IP addresses to groups. These practices tend to minimize the throughput available to every user, but maximize the number of users that can be supported on one backbone.
Furthermore, chips are often not available in order to implement the fastest rates. AMD, for instance, does not support the 32-bit HyperTransport interface on any CPU it has shipped as of the end of 2009. Additionally, WiMAX service providers in the US typically support only up to Template:Val as of the end of 2009.
Choosing service providers or interfaces based on theoretical maxima is unwise, especially for commercial needs. A good example is large scale data centers, which should be more concerned with price per port to support the interface, wattage and heat considerations, and total cost of the solution. Because some protocols such as SCSI and Ethernet now operate many orders of magnitude faster than when originally deployed, scalability of the interface is one major factor, as it prevents costly shifts to technologies that are not backward compatible. Underscoring this is the fact that these shifts often happen involuntarily or by surprise, especially when a vendor abandons support for a proprietary system.
Conventions[edit | edit source]
By convention, bus and network data rates are denoted either in bits per second – bit/s, kbit/s (103 bit/s), Mbit/s (106 bit/s), Gbit/s (109 bit/s), Tbit/s (1012 bit/s) – or bytes per second – B/s, kB/s (103 B/s), MB/s (106 B/s), GB/s (109 B/s), TB/s (1012 B/s). In general, parallel interfaces are quoted in B/s and serial in bit/s. The more commonly used is shown below in bold type.
On devices like modems, bytes may be more than 8 bits long because they may be individually padded out with additional start and stop bits; the figures below will reflect this. Where channels use line codes (such as Ethernet, Serial ATA, and PCI Express), quoted rates are for the decoded signal.
The figures below are simplex data rates, which may conflict with the duplex rates vendors sometimes use in promotional materials. Where two values are listed, the first value is the downstream rate and the second value is the upstream rate.
The use of decimal prefixes is standard in data communications.
Bandwidths[edit | edit source]
The figures below are grouped by network or bus type, then sorted within each group from lowest to highest bandwidth; gray shading indicates a lack of known implementations.
As stated above, all quoted bandwidths are for each direction. Therefore, for duplex interfaces (capable of simultaneous transmission both ways), the stated values are simplex (one way) speeds, rather than total upstream+downstream.
Historical[edit | edit source]
| Technology | Maximum rate | Rate excluding overhead | Year |
|---|---|---|---|
| Smoke signals | millibits/s[1] | Throughout history | |
| Morse code (skilled operator) | Template:Val[lower-alpha 1] | 4 characters per second (cps) (Template:Val)[lower-alpha 2] | 1844 |
| Normal human speech | Template:Val[2] | Prehistoric |
Radio clock[edit | edit source]
Time signal station to radio clock
| Technology | Maximum rate | Year | |
|---|---|---|---|
| IRIG and related | 1 bit/s | ~0.125 characters/s[3][4] | 1960Template:Cn |
Teletypewriter (TTY) or telecommunications device for the deaf (TDD)[edit | edit source]
| Technology | Maximum rate | Year | |
|---|---|---|---|
| TTY (V.18) | Template:Val | 6 characters/s[5] | 1994[6] |
| TTY (V.18) | Template:Val | 6.6 characters/s | 1994 |
| NTSC Line 21 Closed Captioning | Template:Val | ~100 characters/s | 1976[7] |
Modems (narrowband and broadband)[edit | edit source]
Narrowband (POTS: 4 kHz channel)[edit | edit source]
| Technology | Rate | Rate excluding overhead | Year |
|---|---|---|---|
| Teleprinter (50 baud) | Template:Val | 404 operations per minute | 1940x |
| Modem 110 baud (Bell 101) | Template:Val | Template:Val (~10 cps)[lower-alpha 3] | 1959 |
| Modem 300 (300 baud; Bell 103 or V.21) | Template:Val | Template:Val (~30 cps)[lower-alpha 3] | 1962[8] |
| Modem 1200/75 (600 baud; V.23) | Template:Val | Template:Val (~120 cps)[lower-alpha 3] | 1964(?)[9] |
| Modem 1200 (600 baud; Vadic VA3400, Bell 212A, or V.22) | Template:Val | Template:Val (~120 cps)[lower-alpha 3] | 1976 |
| Modem 1200 (Bell 202C, 202D) | Template:Val | Template:Val (~150 cps) | 1976 |
| Modem 2000 (Bell 201A) | Template:Val | Template:Val (~250 cps) | 1962 |
| Modem 2400 (Bell 201B) | Template:Val | Template:Val (~300 cps) | ? |
| Modem 2400 (600 baud; V.22bis) | Template:Val | Template:Val[lower-alpha 3] | 1984[9] |
| Modem 4800/75 (1600 baud; V.27ter) | Template:Val | Template:Val[lower-alpha 3] | 1976[9] |
| Modem 4800 (1600 baud, Bell 208A, 208B) | Template:Val | Template:Val | ? |
| Modem 9600 (2400 baud; V.32) | Template:Val | Template:Val[lower-alpha 3] | 1984[9] |
| Modem 14.4 (2400 baud; V.32bis) | Template:Val | Template:Val[lower-alpha 3] | 1991[8] |
| Modem 28.8 (3200 baud; V.34-1994) | Template:Val | Template:Val[lower-alpha 3] | 1994 |
| Modem 33.6 (3429 baud; V.34-1996/98) | Template:Val | Template:Val[lower-alpha 3] | 1996[9] |
| Modem 56k (8000/3429 baud; V.90) | Template:Val[lower-alpha 4] | Template:Val | 1998 |
| Modem 56k (8000/8000 baud; V.92) | Template:Val[lower-alpha 4] | Template:Val | 2001 |
| Modem data compression (variable; V.92/V.44) | Template:Val[lower-alpha 4] | Template:Val | 2000[9] |
| ISP-side text/image compression (variable) | Template:Val | Template:Val | 1998[9] |
| ISDN Basic Rate Interface (single/dual channel) | Template:Val[lower-alpha 5] | Template:Val | 1986[10] |
| IDSL (dual ISDN + 16 kbit/s data channels) | Template:Val | Template:Val | 2000[11] |
Broadband (hundreds of kHz to GHz wide)[edit | edit source]
Mobile telephone interfaces[edit | edit source]
Wide area networks[edit | edit source]
Local area networks[edit | edit source]
Wireless networks[edit | edit source]
802.11 networks in infrastructure mode are half-duplex; all stations share the medium. In infrastructure or access point mode, all traffic has to pass through an access point (AP). Thus, two stations on the same access point that are communicating with each other must have each and every frame transmitted twice: from the sender to the access point, then from the access point to the receiver. This approximately halves the effective bandwidth.
802.11 networks in ad hoc mode are still half-duplex, but devices communicate directly rather than through an access point. In this mode all devices must be able to see each other, instead of only having to be able to see the access point.
Wireless personal area networks[edit | edit source]
| Technology | Rate | Year | |
|---|---|---|---|
| ANT | Template:Val | Template:Val | |
| IrDA-Control | Template:Val | Template:Val | |
| IrDA-SIR | Template:Val | Template:Val | |
| 802.15.4 (2.4 GHz) | Template:Val | Template:Val | |
| Bluetooth 1.1 | Template:Val | Template:Val | 2002 |
| Bluetooth 2.0+EDR | Template:Val | Template:Val | 2004 |
| IrDA-FIR | Template:Val | Template:Val | |
| IrDA-VFIR | Template:Val | Template:Val | |
| Bluetooth 3.0 | Template:Val | Template:Val | 2009 |
| Bluetooth 4.0 | Template:Val | Template:Val | 2010 |
| Bluetooth 5.0 | Template:Val | Template:Val | 2016 |
| IrDA-UFIR | Template:Val | Template:Val | |
| WUSB-UWB | Template:Val | Template:Val | |
| IrDA-Giga-IR | Template:Val | Template:Val | |
Computer buses[edit | edit source]
Main buses[edit | edit source]
Template:Note label LPC protocol includes high overhead. While the gross data rate equals 33.3 million 4-bit-transfers per second (or Template:Val), the fastest transfer, firmware read, results in Template:Val. The next fastest bus cycle, 32-bit ISA-style DMA write, yields only Template:Val. Other transfers may be as low as Template:Val.[45]
Template:Note label Uses 128b/130b encoding, meaning that about 1.54% of each transfer is used for error detection instead of carrying data between the hardware components at each end of the interface. For example, a single link PCIe 3.0 interface has an 8 Gbit/s transfer rate, yet its usable bandwidth is only about 7.88 Gbit/s.
Template:Note label Uses 8b/10b encoding, meaning that 20% of each transfer is used by the interface instead of carrying data from between the hardware components at each end of the interface. For example, a single link PCIe 1.0 has a 2.5 Gbit/s transfer rate, yet its usable bandwidth is only 2 Gbit/s (250 MB/s).
Template:Note label Uses PAM-4 encoding and a 256 bytes FLIT block, of which 14 bytes are FEC and CRC, meaning that 5.47% of total data rate is used for error detection and correction instead of carrying data. For example, a single link PCIe 6.0 interface has a 64 Gbit/s total transfer rate, yet its usable bandwidth is only 60.5 Gbit/s.
Portable[edit | edit source]
| Technology | Rate | Year | |
|---|---|---|---|
| PC Card 16-bit 255 ns byte mode | Template:Val | Template:Val | 1990 |
| PC Card 16-bit 255 ns word mode | Template:Val | Template:Val | |
| PC Card 16-bit 100 ns byte mode | Template:Val | Template:Val | |
| PC Card 16-bit 100 ns word mode | Template:Val | Template:Val | |
| PC Card 32-bit (CardBus) byte mode | Template:Val | Template:Val | |
| ExpressCard 1.2 USB 2.0 mode | Template:Val | Template:Val | 2003 |
| PC Card 32-bit (CardBus) word mode | Template:Val | Template:Val | |
| PC Card 32-bit (CardBus) doubleword mode | Template:Val | Template:Val | |
| ExpressCard 1.2 PCI Express mode | Template:Val | Template:Val | 2008 |
| ExpressCard 2.0 USB 3.0 mode | Template:Val | Template:Val | |
| ExpressCard 2.0 PCI Express mode | Template:Val | Template:Val | 2009 |
Storage[edit | edit source]
Template:Note label Uses 8b/10b encoding Template:Note label Uses 64b/66b encoding Template:Note label Uses 128b/150b encoding
Peripheral[edit | edit source]
MAC to PHY[edit | edit source]
PHY to XPDR[edit | edit source]
| Technology | Rate | Year | |
|---|---|---|---|
| 10 gigabit/s 16-bit interface (XSBI; 16 lanes) | Template:Val | Template:Val | |
Dynamic random-access memory[edit | edit source]
The table below shows values for PC memory module types. These modules usually combine multiple chips on one circuit board. SIMM modules connect to the computer via an 8-bit- or 32-bit-wide interface. RIMM modules used by RDRAM are 16-bit- or 32-bit-wide.[52] DIMM modules connect to the computer via a 64-bit-wide interface. Some other computer architectures use different modules with a different bus width.
In a single-channel configuration, only one module at a time can transfer information to the CPU. In multi-channel configurations, multiple modules can transfer information to the CPU at the same time, in parallel. FPM, EDO, SDR, and RDRAM memory was not commonly installed in a dual-channel configuration. DDR and DDR2 memory is usually installed in single- or dual-channel configuration. DDR3 memory is installed in single-, dual-, tri-, and quad-channel configurations. Bit rates of multi-channel configurations are the product of the module bit-rate (given below) and the number of channels.
Template:Note label The clock rate at which DRAM memory cells operate. The memory latency is largely determined by this rate. Note that until the introduction of DDR4 the internal clock rate saw relatively slow progress. DDR/DDR2/DDR3 memory uses 2n/4n/8n (respectively) prefetch buffer to provide higher throughput, while the internal memory speed remains similar to that of the previous generation.
Template:Note label The memory speed or clock rate advertised by manufactures and suppliers usually refers to this rate (with 1 GT/s = 1 GHz). Note that modern types of memory use DDR bus with two transfers per clock.
Graphics processing units' RAM[edit | edit source]
RAM memory modules are also utilised by graphics processing units; however, memory modules for those differ somewhat from standard computer memory, particularly with lower power requirements, and are specialised to serve GPUs: for example, GDDR3 was fundamentally based on DDR2. Every graphics memory chip is directly connected to the GPU (point-to-point). The total GPU memory bus width varies with the number of memory chips and the number of lanes per chip. For example, GDDR5 specifies either 16 or 32 lanes per device (chip), while GDDR5X specifies 64 lanes per chip. Over the years, bus widths rose from 64-bit to 512-bit and beyond: e.g. HBM is 1024 bits wide.[53] Because of this variability, graphics memory speeds are sometimes compared per pin. For direct comparison to the values for 64-bit modules shown above, video RAM is compared here in 64-lane lots, corresponding to two chips for those devices with 32-bit widths. In 2012, high-end GPUs used 8 or even 12 chips with 32 lanes each, for a total memory bus width of 256 or 384 bits. Combined with a transfer rate per pin of 5 GT/s or more, such cards could reach 240 GB/s or more.
RAM frequencies used for a given chip technology vary greatly. Where single values are given below, they are examples from high-end cards.[54] Since many cards have more than one pair of chips, the total bandwidth is correspondingly higher. For example, high-end cards often have eight chips, each 32 bits wide, so the total bandwidth for such cards is four times the value given below.
Digital audio[edit | edit source]
| Device | Rate | |
|---|---|---|
| CD Audio (16-bit PCM) | Template:Val | Template:Val |
| I²S | Template:Val @ 24bit/48 kHz | Template:Val |
| AES/EBU | Template:Val @ 24-bit/48 kHz | Template:Val |
| S/PDIF fs 48kHz | Template:Val | Template:Val |
| ADAT Lightpipe (Type I) | Template:Val | 1.152 MB/s |
| AC'97 | Template:Val | Template:Val |
| HDMI | Template:Val | Template:Val |
| DisplayPort | Template:Val | Template:Val |
| Intel High Definition Audio rev. 1.0[62] | Template:Val outbound; 24 Mbit/s inbound | Template:Val outbound; 3 MB/s inbound |
| MADI | Template:Val | Template:Val |
Digital video interconnects[edit | edit source]
Data rates given are from the video source (e.g., video card) to receiving device (e.g., monitor) only. Out of band and reverse signaling channels are not included.
Template:Note label Uses 8b/10b encoding (20% coding overhead) Template:Note label Uses 16b/18b encoding (11% overhead) Template:Note label Uses 128b/132b encoding (3% overhead)
See also[edit | edit source]
- List of Internet access technology bit rates
- Bitrates in multimedia
- Comparison of mobile phone standards
- Comparison of wireless data standards
- OFDM system comparison table
- Optical Carrier transmission rates
- Orders of magnitude (bit rate)
- Sneakernet
- Spectral efficiency comparison table
Notes[edit | edit source]
<templatestyles src="Reflist/styles.css" />
- ↑ Morse can transport 26 alphabetic, 10 numeric and one interword gap plaintext symbols. Transmitting 37 different symbols requires 5.21 bits of information (25.21 = 37). A skilled operator encoding the benchmark "PARIS" plus an interword gap (equal to 31.26 bits) at 40 wpm is operating at an equivalence of 20.84 bit/s.
- ↑ WPM, or words per minute, is the number of times the word "PARIS" is transferred per minute. Strictly speaking the code is quinary, accounting inter-element, inter-letter, and inter-word gaps, yielding 50 binary elements (bits) per one word. Counting characters, including inter-word gaps, gives six characters per word or 240 characters per minute, and finally four characters per second.
- ↑ 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 All modems are wrongly assumed to be in serial operation with 1 start bit, 8 data bits, no parity, and 1 stop bit (2 stop bits for 110-baud modems). Therefore, currently modems are wrongly calculated with transmission of 10 bits per 8-bit byte (11 bits for 110-baud modems). Although the serial port is nearly always used to connect a modem and has equivalent data rates, the protocols, modulations and error correction differ completely.
- ↑ 4.0 4.1 4.2 56K modems: V.90 and V.92 have just 5% overhead for the protocol signalling. The maximum capacity can only be achieved when the upstream (service provider) end of the connection is digital, i.e. a DS0 channel.
- ↑ Effective aggregate bandwidth for an ISDN installation is typically higher than the rates shown for a single channel due to the use of multiple channels. A basic rate interface (BRI) provides two "B" channels and one "D" channel. Each B channel provides 64 kbit/s bandwidth and the "D" channel carries signaling (call setup) information. B channels can be bonded to provide a 128 kbit/s data rate. Primary rate interfaces (PRI) vary depending on whether the region uses E1 (Europe, world) or T1 (North America) bearers. In E1 regions, the PRI carries 30 B-channels and one D-channel; in T1 regions the PRI carries 23 B-channels and one D-channel. The D-channel has different bandwidth on the two interfaces.
- ↑ Most operators only support up to 9600 bit/s
- ↑ SDSL is available in various speeds.
- ↑ ADSL connections will vary in throughput from 64 kbit/s to several Mbit/s depending on configuration. Most are commonly below 2 Mbit/s. Some ADSL and SDSL connections have a higher digital bandwidth than T1 but their rate is not guaranteed, and will drop when the system gets overloaded, whereas the T1 type connections are usually guaranteed and have no contention ratios.
- ↑ Satellite internet may have a high bandwidth but also has a high latency due to the distance between the modem, satellite and hub. One-way satellite connections exist where all the downstream traffic is handled by satellite and the upstream traffic by land-based connections such as 56K modems and ISDN.
- ↑ FireWire natively supports TCP/IP, and is often used at an alternative to Ethernet when connecting 2 nodes.[23]
- ↑ Data rate comparison between FW and Giganet shows that FW's lower overhead has nearly the same throughput as Giganet.[24]
- ↑ 12.0 12.1 12.2 12.3 Note that PCI Express 1.0/2.0 lanes use an 8b/10b encoding scheme.
- ↑ 13.0 13.1 13.2 PCIe 2.0 effectively doubles the bus standard's bandwidth from 2.5 GT/s to 5 GT/s
- ↑ 14.0 14.1 14.2 14.3 14.4 14.5 PCIe 3.0 increases the bandwidth from 5 GT/s to 8 GT/s and switches to 128b-130b encoding
- ↑ SCSI-1, SCSI-2 and SCSI-3 are signaling protocols and do not explicitly refer to a specific rate. Narrow SCSI exists using SCSI-1 and SCSI-2. Higher rates use SCSI-2 or later.
- ↑ Minimum overhead is 38 byte L1/L2, 14 byte AoE per 1024 byte user data
- ↑ Minimum overhead is 38 byte L1/L2, 20 byte IP, 20 byte TCP per 1460 byte user data
- ↑ 18.0 18.1 18.2 18.3 18.4 18.5 Fibre Channel 1GFC, 2GFC, 4GFC use an 8b/10b encoding scheme. Fibre Channel 10GFC, which uses a 64B/66B encoding scheme, is not compatible with 1GFC, 2GFC and 4GFC, and is used only to interconnect switches.
- ↑ 19.0 19.1 Minimum overhead is 38 byte L1/L2, 14 byte AoE per 8192 byte user data
- ↑ 20.0 20.1 20.2 Minimum overhead is 38 byte L1/L2, 20 byte IP, 20 byte TCP per 8960 byte user data
- ↑ 21.0 21.1 21.2 21.3 21.4 21.5 SATA and SAS use an 8b/10b encoding scheme.
- ↑ 22.0 22.1 minimum overhead is 38 byte L1/L2, 36 byte FC per 2048 byte user data
- ↑ Proprietary serial version of IEEE-488 by Commodore International
Script error: No such module "Check for unknown parameters".Script error: No such module "Check for unknown parameters".
References[edit | edit source]
<templatestyles src="Reflist/styles.css" />
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ TTY uses a Baudot code, not ASCII. This uses 5 bits per character instead of 8, plus one start and approx. 1.5 stop bits (7.5 total bits per character sent).
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ 8.0 8.1 Script error: No such module "citation/CS1".
- ↑ 9.0 9.1 9.2 9.3 9.4 9.5 9.6 Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Adam.com.au
- ↑ Script error: No such module "citation/CS1".
- ↑ 13.0 13.1 DOCSIS 1.0 Script error: No such module "webarchive". includes technology which first became available around 1995–1996, and has since become very widely deployed. DOCSIS 1.1 Script error: No such module "webarchive". introduces some security improvements and quality of service (QoS).
- ↑ 14.0 14.1 DOCSIS 2.0 Script error: No such module "webarchive". specifications provide increased upstream throughput for symmetric services.
- ↑ Script error: No such module "citation/CS1".
- ↑ 16.0 16.1 DOCSIS 3.0 Script error: No such module "webarchive". includes support for channel bonding and IPv6.
- ↑ Script error: No such module "citation/CS1".
- ↑ DOCSIS 3.1 Script error: No such module "webarchive". is currently in development by the Cablelabs Consortium
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ 22.0 22.1 "MoCA 1.1 improves throughput" over coaxial cable to 175 Mbit/s versus the 100 Mbit/s provided by the MoCA 1.0 specification.
- ↑ Tweaktown.com
- ↑ Unibrain.com Script error: No such module "webarchive".
- ↑ 25.00 25.01 25.02 25.03 25.04 25.05 25.06 25.07 25.08 25.09 25.10 25.11 25.12 InfiniBand SDR, DDR and QDR use an 8b/10b encoding scheme.
- ↑ 26.00 26.01 26.02 26.03 26.04 26.05 26.06 26.07 26.08 26.09 26.10 26.11 26.12 26.13 26.14 26.15 26.16 26.17 26.18 26.19 26.20 26.21 26.22 26.23 26.24 26.25 26.26 26.27 InfiniBand FDR-10, FDR and EDR use a 64b/66b encoding scheme.
- ↑ 27.0 27.1 27.2 27.3 Script error: No such module "citation/CS1".
- ↑ Mac History
- ↑ VAW: Apple IIgs Specs Script error: No such module "webarchive".
- ↑ Script error: No such module "citation/CS1".
- ↑ The Zorro II bus use 4 clocks per 16-Bit of data transferred. See the Zorro III technical specification Script error: No such module "webarchive". for more information.
- ↑ Japan wikipedia article, Bus used in early NEC PC-9800 series and compatible systems
- ↑ STD 32 Bus Specification and Designer's Guide
- ↑ Japan wikipedia article, Bus used in later NEC PC-9800 series and compatible systems
- ↑ RISC System/6000 POWERstation/POWERserver 580
- ↑ Local Area Networks Newsletter by Paul Polishuk, September 1992, Page 7 (APbus used in Sony NeWS and NEC UP4800 workstations and NEC EWS4800 servers after VMEbus and before switch to PCI)
- ↑ Japan wikipedia article, Bus used in NEC PC-9821 series
- ↑ Dave Haynie, designer of the Zorro III bus, claims in this posting that the theoretical max of the Zorro III bus can be derived by the timing information given in chapter 5 of the Zorro III technical specification Script error: No such module "webarchive"..
- ↑ Dave Haynie, designer of the Zorro III bus, states in this posting that Zorro III is an asynchronous bus and therefore does not have a classical MHz rating. A maximum theoretical MHz value may be derived by examining timing constraints detailed in the Zorro III technical specification Script error: No such module "webarchive"., which should yield about 37.5 MHz. No existing implementation performs to this level.
- ↑ Dave Haynie, designer of the Zorro III bus, claims in this posting that Zorro III has a max burst rate of 150 MB/s.
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Intel LPC Interface Specification 1.1
- ↑ Script error: No such module "citation/CS1".
- ↑ 47.0 47.1 47.2 FireWire (IEEE 1394b) uses an 8b/10b encoding scheme.
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Template:Cite press release
- ↑ Script error: No such module "citation/CS1".
- ↑ Comparison of AMD graphics processing units
- ↑ Comparison of Nvidia graphics processing units
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ 58.0 58.1 Script error: No such module "citation/CS1".
- ↑ 59.0 59.1 59.2 Script error: No such module "citation/CS1".
- ↑ 60.0 60.1 Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ High Definition Audio Specification, Revision 1.0a, 2010
- ↑ Videsignline.com, Panel display interfaces and bandwidth: From TTL, LVDS, TDMS to DisplayPort
- ↑ Script error: No such module "citation/CS1".
- ↑ 65.0 65.1 65.2 Displayport Technical Overview Script error: No such module "webarchive"., May 2010
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
Script error: No such module "Check for unknown parameters".
External links[edit | edit source]
- Interconnection Speeds Compared
- LTE Categories 1
- LTE Categories 2
- Need for Speed: Theoretical Bandwidth Comparison – A graph illustrating digital bandwidths. Digital Silence, 2004 (archived).
Script error: No such module "Navbox".
