![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 |
Please add new topics to the bottom of the page. —Preceding unsigned comment added by Theaveng ( talk • contribs) 16:53, 3 December 2007 (UTC)
Hi. Why are we splitting up different types of wireless? Would be nice if they were together so people could compare. I find the existing splits kind of arbitrary, given that uses can change (e.g. 802.11 being used for neighborhood mesh networks) -- Treekids ( talk) 22:03, 7 January 2008 (UTC)
Google finds lots of hits to OC-256, but after clicking a huge number of them, none provide more detail than a speed. I can not find any reference to equipment or standards related to such a speed, so I've removed it. As further example of this mindless copy-and-pasting across the internet, OC-255 also produces hits, yet is most certainly not real. Mrand 14:26, 21 March 2006 (UTC)
The first makes comparision between full and half duplex links easier, the second sounds technically more correct to me. Mixing both causes confusion.
I've have a very similar page for years.
Note I used MB/s (that's 10^6 bytes per second) throughout as that is the most common unit of speed/size that people work with in computer systems currently.
Perhaps a link to my page would be appropriate?
With the variety of units it is dificult to compute the volume of information here. I suggest including some kind of graph for each section, to depict differences in speed. The only barrier I see to this is making something that can be edited later by anyone, so that leaves out images. Perhaps a text format, like a pipe for each 500 bits, or something? -- Digitalgadget 05:45, 11 September 2006 (UTC)
Please discuss this prototype.
My intention is to provide some kind of visual comparison. In creating this file, the main problem I see is portraying tiny values with huge ones, which I tried to solve here by jumping to powers of ten. --
Digitalgadget
02:45, 20 February 2007 (UTC)
Would it be possible to (mis-)use meta:EasyTimeline to create these graphs? EasyTimeline makes it easy for anyone to edit a graph in text format. -- 68.0.120.35 04:20, 18 August 2007 (UTC)
Thanks! I can see this working with a lot of effort. Perhaps someone with a strong programming background could use EasyTimeline as a template for making a table meta. Or maybe one exists and I am too new to know where to look. The hard part will be appropriately representing the minute differences between speeds while making it easy to see both ends of a wide spectrum (as I have mentioned before). -- 67.160.113.95 17:38, 19 August 2007 (UTC) -- DigitalGadget 17:40, 19 August 2007 (UTC) (log in timed out)
Only way (at least that to me is satisfactory) to compare such differing values is using a log scale. Trouble is that's confusing to a lot of people. M0ffx 00:45, 2 October 2007 (UTC)
I removed the SAS-2 entry because the spec isn't finalized yet, as of 1/17/2007, and I couldn't nail down the operating speeds. Feel free to replace it with correct numbers, if you can. "6Gbit/s" and "600MB/s" don't correlate. |- | Serial Attached SCSI 2 || 6 Gbit/s || 600 MB/s 206.165.137.194 02:33, 23 January 2007 (UTC)
I made a big edit and I moved all the content of the references and linked them with the <ref> tag. I hope you don't mind. Feel free to edit. -- Ysangkok 17:13, 21 January 2007 (UTC)
I would like to see eSATA added to the "Computer interfaces (external)" section. But I am no expert. So someone else maybe could do this?
Additionally to what already have been said I wonder whether anyone ever checked whether the numbers listed are with or without protocol overhead, or somewhere between?
For example here's DOCSIS 2.0, which contains not only packets but all kinds of dirty tricks to make sure the data arrives through a noisy wire, they use variable sized forward error correction, different size encapsulations, etc.
I would guess these values are all raw bit transfer rates, which means that the BYTES column means even less than I tried to emphasize in the notes; with "theoretical" 43Mbits which includes noise, packet headers, checksums, FEC, and god knows what, it may be well much less useful-bits-in-second, which gives then useful bytes-per-sec times 8...
And there is IP and TCP protocol overheads too. For example for an ftp transfer it means 52 bytes for every 1500 bytes (at least for those packets I just checked) which is ~1.035 difference.
The BYTES column is a good approximation, but I believe its imprecisity(sp?) should be emphasized. -- grin ✎ 09:43, 29 January 2007 (UTC)
I don't think it's possible. Even DOCSIS - which is "just one cable tv net protocol" - defines dozens of encoding combinations, and throughput depends even on the data sent. I just wanted to justify my warning in the notes, because someone referred me to this page and I kindly wanted to prevent people to believe the B/s value is holy grail. :-) -- grin ✎ 01:20, 31 January 2007 (UTC)
If we assume that 1MB = 8Mbit, giga=1000 mega this is correct::
and this is NOT::
We just can NOT declare, that 300X=2.4Y in one line -- and NEXT line below that 300X=3Y :|. BTW: Gbits are signaling rate and MB are throughput.
Just FYI::
SAS supports higher transfer speed (1.5, 3.0 or 6.0 Gbps). SAS supports point data transfer speeds up to 3 Gbit/s, but is expected to reach 12 Gbit/s by the year 2012. —Preceding
unsigned comment added by
Jan Kunder (
talk •
contribs)
As this page is edited and evolves into something more complex, please keep in mind that this content needs to be easily understood by ordinary folks. For instance, the idea of organizing the table by "Order of magnitude of bandwidths" may result in greater technical accuracy, but it is much easier to find specific device specifications in the current table format, and it also is much easier to read and comprehend the information because similar device/connections are grouped together (for the most part) and seperated by bold headlines. It's not perfect, but as is, the list is easier for those of us who are NOT engineers! The proposed new table organization makes it very difficult to quickly scan the table and find something...Perhaps a link to an alternative "order of magnitude" version of the table would be helpful, but please, don't replace the existing table...
It would be very helpful if Ethernet cable specifications and bandwidth were added to this list, such as Cat 5, Cat 5e, Cat 6, etc. This seems necessary because components with the appropriate technical specifications must be used to connect all these various technologies together and achieve the bandwidths listed. Geopix 07:52, 25 May 2007 (UTC)geopix
If both are named in the article, the difference should be pointed out. (If in almost all cases the numbers quoted by manufacturers etc is Bandwidth, then I see no reason to mention channel capacity at all in the first place.). Iron Condor 18:40, 29 May 2007 (UTC)
Why is the "Connection" column now flush right, instead of flush left (as I believe it once was)? This is very bad graphic design in a table like this. There are times to use flush right alignment in tables, but in this case, the column contents have become more difficult to read. Flush left alignment allows readers to quickly scan each section, find the device they are seeking and see the bandwidth. Flush right might have worked if the variations in device name line widths weren't so great, but it does not work — at all — in this instance. Please, fix this. Geopix 12:46, 18 June 2007 (UTC)GEOPIX
Hi - I stumbled upon this while researching comparative effective speeds for mobile wireless networks. This is an excellent cheat sheet and very useful! However a few comments. - I am going to add a link to CDMA2000#CDMA2000_1xRTT - I think the ISDN section needs clarification - most people are going to be looking for "what is my effective bandwidth" - and for basic ISDN US aggregate bandwidth for Basic rate interface is 128 kbps,etc see [1]-- Boscobiscotti 16:25, 27 June 2007 (UTC)
If we are going to falsely title an article with the term " bandwidth" even though the article is really about channel capacity not bandwidth, could we at least actually include the bandwidth in the table? I was hoping to find the bandwidth (Hz) of some items and this article seems like the place to look. Alas, it is not. -- Miken2005 08:33, 8 July 2007 (UTC)
If you like. A quick look at a few of the linked articles found one using "bandwidth" literally, several lacking the word, and several using it to mean transfer rate. I surmise that it is rare to quote literal bandwidth at all. Perhaps you should start in the linked articles, adding literal bandwidths when you can find them. Once you've got half a dozen, you can start including them in this list in parentheses, and when there are a dozen or two, perhaps that's the time that the table should have another column. Jim.henderson 20:41, 12 July 2007 (UTC)
The table is not laying out correctly, and my knowledge of Wikitables isn't good enough to resolve this. I was trying to put a comment in the text so that well-meaning editors don't change the modem figures back to 8 bits/octet/byte when I discovered this. Could some kind soul rescue the table - and while we are at it, could we put the notes at the bottom of each section, where they belong, rather than at the end of the article. Thanks. WLD talk| edits 17:32, 13 July 2007 (UTC)
This will allow for better understanding and comparison of the various technologies —Preceding unsigned comment added by 91.113.23.134 ( talk) 06:59, August 27, 2007 (UTC)
I can't seem to locate bandwidth mentions for things like PCMCIA, PC-Card, Expresscard -- i.e. technologies typically used to extend laptop buses. Was this an intentional exclusion?
Shouldn't the Local area network be before the Wide area network? It just seems more natural to me. 89.120.124.53 10:20, 20 December 2006 (UTC)
This list is painfully lacking. I don't see VLB, EISA, or MCA on the list, to name a few of the more prominent 1990s bus technologies. 71.116.217.242 20:09, 28 June 2006 (UTC)
HyperTransport supports an auto-negotiated bus width, based on two 2-bit lines to 32-bit lines. The full-sized, full-speed, 32-bit bus in each direction has a transfer rate of 20,800 MByte/s (2*(32/8)*2600), making it much faster than many existing standards. Buses of various widths can be mixed together into a single application (for example, 2x8 instead of 1x16), which allows for higher speed buses between main memory and the CPU, and lower speed buses among peripherals as appropriate. The technology also has much lower latency than other solutions.
This is the fastest bus, and i miss this in the list
Someone deleted the entry for the 110 baud modem. They did actually exist. See [2] and [3]. WLD 08:25, 29 August 2006 (UTC)
(WAS: "Photos or graphs")
With the variety of units it is dificult to compute the volume of information here. I suggest including some kind of graph for each section, to depict differences in speed. The only barrier I see to this is making something that can be edited later by anyone, so that leaves out images. Perhaps a text format, like a pipe for each 500 bits, or something? -- Digitalgadget 05:45, 11 September 2006 (UTC)
The article here states 1Gb token ring exists, however nowhere else can I see 1Gb token ring, even on the token ring article. —Preceding unsigned comment added by 68.82.202.52 ( talk) 17:12, 3 October 2007 (UTC)
Come to think of it: where did the 4.16 MBit/s figure come from? The token ring article states the original token ring ran at 4 MBit/s (which as far as I know, is correct, if by original token ring the author is referring to the IBM network later standardised by 802.5) 144.32.136.46 14:04, 13 October 2007 (UTC)
Your attempt to change the Bandwidth article to a Anti-USB point-of-view has been reverted. This is an encyclopedia, not a place for you to enter your non-sourced opinions & comments. Thank you. - Theaveng 11:08, 19 October 2007 (UTC)
Hi for a fair comparision between devices I'd like to see the sustained and burst speeds. IE USB High Speed has a burst speed that does not fair well as compaired to Firewire 400.
Thanks
Neil C.
i'm not sure what the plural form of bus is. I'd like to see some other common bus' here, such as sbus (25MHz 64 bit iirc) the GIO line, gio 32, gio 64, vmE, NuBus (32 bit at 10, or 20MHz) I belive HP had a few bus' used in their systems. There's also the bus Intel's been using for gigabit ethernet, the name escapes me, and in addition to those, are the connections used between the northbridge and the south bridge. I believe VIA calls theirs V-link. also single and dual link dvi might be interesting.
The data rates listed seem all over the place. It also may supports or is split into 3 speeds, just do not know the speeds. http://www.adept.net.au/grabbers/coreco/pccamlink.shtml
http://www.machinevisiononline.org/public/articles/archivedetails.cfm?id=1528 255, 382, 680MBps (x8 for Mbps)
http://aegiselect.com/products/cameralink-cameras.html "Camera Link® technology features the combination of both high-speeds (1.2, 2.4, & 3.6 Gbps) and high-resolution imaging."
http://www.tmworld.com/article/CA377231.html "The three levels accommodate the wider data paths required by multi-tap cameras (with more than one video-output stream) and allow for future expansion. The full Camera Link configuration achieves an effective bandwidth of 4.8 Gbps."
-- Flightsoffancy ( talk) 21:54, 9 January 2008 (UTC)
Well, I had time at work (since we work with it) to read up on it, and learn the details.
I have updated both this and the CL page.
Excellent info to have.
--
Flightsoffancy (
talk)
14:13, 22 January 2008 (UTC)
Hi, it looks like there is the one ore another error in the table. NFS over Infiniband 120000 Mbit/s 12000 MB/s iSCSI over 100G Ethernet (Planned) 100000 Mbit/s 12500 MB/s How it could be that NFS is faster in bits but slower in bytes than iSCSI ? it would be also nice if the units are more or less the same.... i mean sometimes KB and sometimes kB in the byte column. Bold and none Bold is also mixed. and sometimes there ar seperators for thousand and sometimes not. —Preceding unsigned comment added by AssetBurned ( talk • contribs) 17:29, 14 January 2008 (UTC)
For example: FireWire 393.216 Mbit/s . Has the speed truly been measured to 6 signifigant digits of accuracy? I would think "393 Mbit/s" would be good enough (especially since most of these numbers are theoretical, not real-world values). ----- There are a couple other data values given that are also overly precise IMHO. :-) Theaveng ( talk) 22:23, 28 January 2008 (UTC)
After thinking about the changes that another user and I made earlier this afternoon, I think that it would be best to reorganize the article as follows:
69.140.152.55 ( talk) 23:00, 28 January 2008 (UTC)
I just dont do this because i dont have availble time, im in the working time now. but it would be cool if the lists provide the user on the top of each columm a button that sort the entries by name, or velocity, so the people can find the information that they need faster than using ctrl+f thanx dudes —Preceding unsigned comment added by Ogat ( talk • contribs) 20:45, 18 February 2008 (UTC)
I'd like to know the speeds that one can get over raw POTS, raw cable, and raw fiber. For example, cable typically carries dozens of TV channels plus who knows how many DOCSIS cable internet connections; I'd like to know how much data could theoretically be pushed across a cable. Ditto for POTS and fiber. Get out your time machine and tell me what you think Wikipedia will say, about 100 years from now, what the max customer and provider bandwidths will be for them. I'm sure there are specs out there, I just haven't been able to find them. It looks like DSL is already up to 250Mbps, much higher than I thought it could go. -- Scott McNay ( talk) 13:15, 7 April 2008 (UTC)
The conversion between gigabits-per-second and megabytes-per-second is incorrect for Fibre Channel, SAS, SATA, and Infiniband. These protocols incorporate the 8b/10b encoding method. An 8-bit byte is converted to a 10-bit transmission character. Thus to convert from bit-rate to byte-rate one divides by 10, not 8. Fibre Channel products are avilable today, off the shelf, at 1, 2 and 4 gigabits per second (Gb/s) which in bytes is 100, 200, and 400 megabytes per second (MB/s). Note the lower case 'b' for bits and upper case 'B' for bytes. Ten gig Fibre Channel is on the horizon. These data rates are simplex. Fibre Channel is fully duplex so marketeers like to double these numbers, which is permissable from an engineering point of view. It is difficult to find computers and disk drives that can read and write at full speed in both directions at the same time but it is still technically correct to advertize it that way. SAS and SATA products are presently available at 1.5 Gb/s and 3 Gb/s with 6 Gb/s products appearing in private technology demonstrations (it is now Spring 2008). I don't play with Infiniband so I'm not sure what is available there. There is one notable difference between Fibre Channel and SAS/SATA. Fibre Channel was the first protocol to utilize the 8b/10b encoding scheme. The original architects wanted Fibre Channel to deliver 100 megabytes per second under true operating conditions. When it became apparent that the protocol would impose a performance penalty of 6.25% they increased the clock rate from 1.000 Gb/s to 1.0625 Gb/s to compensate. Thus, Fibre Channel operating at the base rate of 1.0625 Gb/s truely delivers 100 MB/s in real-world operating conditions. In Fibre Channel this concept scales to the higher speeds also. The same is not true for SAS and SATA. The penalty imposed by the protol is not compensated. Still, in the SAS/SATA world it is common to claim 3 gigabit transmission rates equate to 300 megabyte data transfer rates and so forth. Like Fibre Channel, SAS and SATA are full duplex technologies. One needs to be careful when reading the advertizements whether the quoted rates are simplex or duplex.
Ken Stewart gordon_ken_stewart@msn.com —Preceding unsigned comment added by 207.224.123.54 ( talk • contribs) 18:24, April 19, 2008
it might be helpful to add a column with a two or three character that indicates whether the device is capable of a duplex connection, whether duplex connection is symmetrical, and an optional footnote.
(footnotes would permit adding info on things like asymmetrical upload/download rates while keeping the table width reasonable.) —Preceding unsigned comment added by 69.253.239.161 ( talk) 18:49, 22 April 2008 (UTC)
![]() | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 |
Please add new topics to the bottom of the page. —Preceding unsigned comment added by Theaveng ( talk • contribs) 16:53, 3 December 2007 (UTC)
Hi. Why are we splitting up different types of wireless? Would be nice if they were together so people could compare. I find the existing splits kind of arbitrary, given that uses can change (e.g. 802.11 being used for neighborhood mesh networks) -- Treekids ( talk) 22:03, 7 January 2008 (UTC)
Google finds lots of hits to OC-256, but after clicking a huge number of them, none provide more detail than a speed. I can not find any reference to equipment or standards related to such a speed, so I've removed it. As further example of this mindless copy-and-pasting across the internet, OC-255 also produces hits, yet is most certainly not real. Mrand 14:26, 21 March 2006 (UTC)
The first makes comparision between full and half duplex links easier, the second sounds technically more correct to me. Mixing both causes confusion.
I've have a very similar page for years.
Note I used MB/s (that's 10^6 bytes per second) throughout as that is the most common unit of speed/size that people work with in computer systems currently.
Perhaps a link to my page would be appropriate?
With the variety of units it is dificult to compute the volume of information here. I suggest including some kind of graph for each section, to depict differences in speed. The only barrier I see to this is making something that can be edited later by anyone, so that leaves out images. Perhaps a text format, like a pipe for each 500 bits, or something? -- Digitalgadget 05:45, 11 September 2006 (UTC)
Please discuss this prototype.
My intention is to provide some kind of visual comparison. In creating this file, the main problem I see is portraying tiny values with huge ones, which I tried to solve here by jumping to powers of ten. --
Digitalgadget
02:45, 20 February 2007 (UTC)
Would it be possible to (mis-)use meta:EasyTimeline to create these graphs? EasyTimeline makes it easy for anyone to edit a graph in text format. -- 68.0.120.35 04:20, 18 August 2007 (UTC)
Thanks! I can see this working with a lot of effort. Perhaps someone with a strong programming background could use EasyTimeline as a template for making a table meta. Or maybe one exists and I am too new to know where to look. The hard part will be appropriately representing the minute differences between speeds while making it easy to see both ends of a wide spectrum (as I have mentioned before). -- 67.160.113.95 17:38, 19 August 2007 (UTC) -- DigitalGadget 17:40, 19 August 2007 (UTC) (log in timed out)
Only way (at least that to me is satisfactory) to compare such differing values is using a log scale. Trouble is that's confusing to a lot of people. M0ffx 00:45, 2 October 2007 (UTC)
I removed the SAS-2 entry because the spec isn't finalized yet, as of 1/17/2007, and I couldn't nail down the operating speeds. Feel free to replace it with correct numbers, if you can. "6Gbit/s" and "600MB/s" don't correlate. |- | Serial Attached SCSI 2 || 6 Gbit/s || 600 MB/s 206.165.137.194 02:33, 23 January 2007 (UTC)
I made a big edit and I moved all the content of the references and linked them with the <ref> tag. I hope you don't mind. Feel free to edit. -- Ysangkok 17:13, 21 January 2007 (UTC)
I would like to see eSATA added to the "Computer interfaces (external)" section. But I am no expert. So someone else maybe could do this?
Additionally to what already have been said I wonder whether anyone ever checked whether the numbers listed are with or without protocol overhead, or somewhere between?
For example here's DOCSIS 2.0, which contains not only packets but all kinds of dirty tricks to make sure the data arrives through a noisy wire, they use variable sized forward error correction, different size encapsulations, etc.
I would guess these values are all raw bit transfer rates, which means that the BYTES column means even less than I tried to emphasize in the notes; with "theoretical" 43Mbits which includes noise, packet headers, checksums, FEC, and god knows what, it may be well much less useful-bits-in-second, which gives then useful bytes-per-sec times 8...
And there is IP and TCP protocol overheads too. For example for an ftp transfer it means 52 bytes for every 1500 bytes (at least for those packets I just checked) which is ~1.035 difference.
The BYTES column is a good approximation, but I believe its imprecisity(sp?) should be emphasized. -- grin ✎ 09:43, 29 January 2007 (UTC)
I don't think it's possible. Even DOCSIS - which is "just one cable tv net protocol" - defines dozens of encoding combinations, and throughput depends even on the data sent. I just wanted to justify my warning in the notes, because someone referred me to this page and I kindly wanted to prevent people to believe the B/s value is holy grail. :-) -- grin ✎ 01:20, 31 January 2007 (UTC)
If we assume that 1MB = 8Mbit, giga=1000 mega this is correct::
and this is NOT::
We just can NOT declare, that 300X=2.4Y in one line -- and NEXT line below that 300X=3Y :|. BTW: Gbits are signaling rate and MB are throughput.
Just FYI::
SAS supports higher transfer speed (1.5, 3.0 or 6.0 Gbps). SAS supports point data transfer speeds up to 3 Gbit/s, but is expected to reach 12 Gbit/s by the year 2012. —Preceding
unsigned comment added by
Jan Kunder (
talk •
contribs)
As this page is edited and evolves into something more complex, please keep in mind that this content needs to be easily understood by ordinary folks. For instance, the idea of organizing the table by "Order of magnitude of bandwidths" may result in greater technical accuracy, but it is much easier to find specific device specifications in the current table format, and it also is much easier to read and comprehend the information because similar device/connections are grouped together (for the most part) and seperated by bold headlines. It's not perfect, but as is, the list is easier for those of us who are NOT engineers! The proposed new table organization makes it very difficult to quickly scan the table and find something...Perhaps a link to an alternative "order of magnitude" version of the table would be helpful, but please, don't replace the existing table...
It would be very helpful if Ethernet cable specifications and bandwidth were added to this list, such as Cat 5, Cat 5e, Cat 6, etc. This seems necessary because components with the appropriate technical specifications must be used to connect all these various technologies together and achieve the bandwidths listed. Geopix 07:52, 25 May 2007 (UTC)geopix
If both are named in the article, the difference should be pointed out. (If in almost all cases the numbers quoted by manufacturers etc is Bandwidth, then I see no reason to mention channel capacity at all in the first place.). Iron Condor 18:40, 29 May 2007 (UTC)
Why is the "Connection" column now flush right, instead of flush left (as I believe it once was)? This is very bad graphic design in a table like this. There are times to use flush right alignment in tables, but in this case, the column contents have become more difficult to read. Flush left alignment allows readers to quickly scan each section, find the device they are seeking and see the bandwidth. Flush right might have worked if the variations in device name line widths weren't so great, but it does not work — at all — in this instance. Please, fix this. Geopix 12:46, 18 June 2007 (UTC)GEOPIX
Hi - I stumbled upon this while researching comparative effective speeds for mobile wireless networks. This is an excellent cheat sheet and very useful! However a few comments. - I am going to add a link to CDMA2000#CDMA2000_1xRTT - I think the ISDN section needs clarification - most people are going to be looking for "what is my effective bandwidth" - and for basic ISDN US aggregate bandwidth for Basic rate interface is 128 kbps,etc see [1]-- Boscobiscotti 16:25, 27 June 2007 (UTC)
If we are going to falsely title an article with the term " bandwidth" even though the article is really about channel capacity not bandwidth, could we at least actually include the bandwidth in the table? I was hoping to find the bandwidth (Hz) of some items and this article seems like the place to look. Alas, it is not. -- Miken2005 08:33, 8 July 2007 (UTC)
If you like. A quick look at a few of the linked articles found one using "bandwidth" literally, several lacking the word, and several using it to mean transfer rate. I surmise that it is rare to quote literal bandwidth at all. Perhaps you should start in the linked articles, adding literal bandwidths when you can find them. Once you've got half a dozen, you can start including them in this list in parentheses, and when there are a dozen or two, perhaps that's the time that the table should have another column. Jim.henderson 20:41, 12 July 2007 (UTC)
The table is not laying out correctly, and my knowledge of Wikitables isn't good enough to resolve this. I was trying to put a comment in the text so that well-meaning editors don't change the modem figures back to 8 bits/octet/byte when I discovered this. Could some kind soul rescue the table - and while we are at it, could we put the notes at the bottom of each section, where they belong, rather than at the end of the article. Thanks. WLD talk| edits 17:32, 13 July 2007 (UTC)
This will allow for better understanding and comparison of the various technologies —Preceding unsigned comment added by 91.113.23.134 ( talk) 06:59, August 27, 2007 (UTC)
I can't seem to locate bandwidth mentions for things like PCMCIA, PC-Card, Expresscard -- i.e. technologies typically used to extend laptop buses. Was this an intentional exclusion?
Shouldn't the Local area network be before the Wide area network? It just seems more natural to me. 89.120.124.53 10:20, 20 December 2006 (UTC)
This list is painfully lacking. I don't see VLB, EISA, or MCA on the list, to name a few of the more prominent 1990s bus technologies. 71.116.217.242 20:09, 28 June 2006 (UTC)
HyperTransport supports an auto-negotiated bus width, based on two 2-bit lines to 32-bit lines. The full-sized, full-speed, 32-bit bus in each direction has a transfer rate of 20,800 MByte/s (2*(32/8)*2600), making it much faster than many existing standards. Buses of various widths can be mixed together into a single application (for example, 2x8 instead of 1x16), which allows for higher speed buses between main memory and the CPU, and lower speed buses among peripherals as appropriate. The technology also has much lower latency than other solutions.
This is the fastest bus, and i miss this in the list
Someone deleted the entry for the 110 baud modem. They did actually exist. See [2] and [3]. WLD 08:25, 29 August 2006 (UTC)
(WAS: "Photos or graphs")
With the variety of units it is dificult to compute the volume of information here. I suggest including some kind of graph for each section, to depict differences in speed. The only barrier I see to this is making something that can be edited later by anyone, so that leaves out images. Perhaps a text format, like a pipe for each 500 bits, or something? -- Digitalgadget 05:45, 11 September 2006 (UTC)
The article here states 1Gb token ring exists, however nowhere else can I see 1Gb token ring, even on the token ring article. —Preceding unsigned comment added by 68.82.202.52 ( talk) 17:12, 3 October 2007 (UTC)
Come to think of it: where did the 4.16 MBit/s figure come from? The token ring article states the original token ring ran at 4 MBit/s (which as far as I know, is correct, if by original token ring the author is referring to the IBM network later standardised by 802.5) 144.32.136.46 14:04, 13 October 2007 (UTC)
Your attempt to change the Bandwidth article to a Anti-USB point-of-view has been reverted. This is an encyclopedia, not a place for you to enter your non-sourced opinions & comments. Thank you. - Theaveng 11:08, 19 October 2007 (UTC)
Hi for a fair comparision between devices I'd like to see the sustained and burst speeds. IE USB High Speed has a burst speed that does not fair well as compaired to Firewire 400.
Thanks
Neil C.
i'm not sure what the plural form of bus is. I'd like to see some other common bus' here, such as sbus (25MHz 64 bit iirc) the GIO line, gio 32, gio 64, vmE, NuBus (32 bit at 10, or 20MHz) I belive HP had a few bus' used in their systems. There's also the bus Intel's been using for gigabit ethernet, the name escapes me, and in addition to those, are the connections used between the northbridge and the south bridge. I believe VIA calls theirs V-link. also single and dual link dvi might be interesting.
The data rates listed seem all over the place. It also may supports or is split into 3 speeds, just do not know the speeds. http://www.adept.net.au/grabbers/coreco/pccamlink.shtml
http://www.machinevisiononline.org/public/articles/archivedetails.cfm?id=1528 255, 382, 680MBps (x8 for Mbps)
http://aegiselect.com/products/cameralink-cameras.html "Camera Link® technology features the combination of both high-speeds (1.2, 2.4, & 3.6 Gbps) and high-resolution imaging."
http://www.tmworld.com/article/CA377231.html "The three levels accommodate the wider data paths required by multi-tap cameras (with more than one video-output stream) and allow for future expansion. The full Camera Link configuration achieves an effective bandwidth of 4.8 Gbps."
-- Flightsoffancy ( talk) 21:54, 9 January 2008 (UTC)
Well, I had time at work (since we work with it) to read up on it, and learn the details.
I have updated both this and the CL page.
Excellent info to have.
--
Flightsoffancy (
talk)
14:13, 22 January 2008 (UTC)
Hi, it looks like there is the one ore another error in the table. NFS over Infiniband 120000 Mbit/s 12000 MB/s iSCSI over 100G Ethernet (Planned) 100000 Mbit/s 12500 MB/s How it could be that NFS is faster in bits but slower in bytes than iSCSI ? it would be also nice if the units are more or less the same.... i mean sometimes KB and sometimes kB in the byte column. Bold and none Bold is also mixed. and sometimes there ar seperators for thousand and sometimes not. —Preceding unsigned comment added by AssetBurned ( talk • contribs) 17:29, 14 January 2008 (UTC)
For example: FireWire 393.216 Mbit/s . Has the speed truly been measured to 6 signifigant digits of accuracy? I would think "393 Mbit/s" would be good enough (especially since most of these numbers are theoretical, not real-world values). ----- There are a couple other data values given that are also overly precise IMHO. :-) Theaveng ( talk) 22:23, 28 January 2008 (UTC)
After thinking about the changes that another user and I made earlier this afternoon, I think that it would be best to reorganize the article as follows:
69.140.152.55 ( talk) 23:00, 28 January 2008 (UTC)
I just dont do this because i dont have availble time, im in the working time now. but it would be cool if the lists provide the user on the top of each columm a button that sort the entries by name, or velocity, so the people can find the information that they need faster than using ctrl+f thanx dudes —Preceding unsigned comment added by Ogat ( talk • contribs) 20:45, 18 February 2008 (UTC)
I'd like to know the speeds that one can get over raw POTS, raw cable, and raw fiber. For example, cable typically carries dozens of TV channels plus who knows how many DOCSIS cable internet connections; I'd like to know how much data could theoretically be pushed across a cable. Ditto for POTS and fiber. Get out your time machine and tell me what you think Wikipedia will say, about 100 years from now, what the max customer and provider bandwidths will be for them. I'm sure there are specs out there, I just haven't been able to find them. It looks like DSL is already up to 250Mbps, much higher than I thought it could go. -- Scott McNay ( talk) 13:15, 7 April 2008 (UTC)
The conversion between gigabits-per-second and megabytes-per-second is incorrect for Fibre Channel, SAS, SATA, and Infiniband. These protocols incorporate the 8b/10b encoding method. An 8-bit byte is converted to a 10-bit transmission character. Thus to convert from bit-rate to byte-rate one divides by 10, not 8. Fibre Channel products are avilable today, off the shelf, at 1, 2 and 4 gigabits per second (Gb/s) which in bytes is 100, 200, and 400 megabytes per second (MB/s). Note the lower case 'b' for bits and upper case 'B' for bytes. Ten gig Fibre Channel is on the horizon. These data rates are simplex. Fibre Channel is fully duplex so marketeers like to double these numbers, which is permissable from an engineering point of view. It is difficult to find computers and disk drives that can read and write at full speed in both directions at the same time but it is still technically correct to advertize it that way. SAS and SATA products are presently available at 1.5 Gb/s and 3 Gb/s with 6 Gb/s products appearing in private technology demonstrations (it is now Spring 2008). I don't play with Infiniband so I'm not sure what is available there. There is one notable difference between Fibre Channel and SAS/SATA. Fibre Channel was the first protocol to utilize the 8b/10b encoding scheme. The original architects wanted Fibre Channel to deliver 100 megabytes per second under true operating conditions. When it became apparent that the protocol would impose a performance penalty of 6.25% they increased the clock rate from 1.000 Gb/s to 1.0625 Gb/s to compensate. Thus, Fibre Channel operating at the base rate of 1.0625 Gb/s truely delivers 100 MB/s in real-world operating conditions. In Fibre Channel this concept scales to the higher speeds also. The same is not true for SAS and SATA. The penalty imposed by the protol is not compensated. Still, in the SAS/SATA world it is common to claim 3 gigabit transmission rates equate to 300 megabyte data transfer rates and so forth. Like Fibre Channel, SAS and SATA are full duplex technologies. One needs to be careful when reading the advertizements whether the quoted rates are simplex or duplex.
Ken Stewart gordon_ken_stewart@msn.com —Preceding unsigned comment added by 207.224.123.54 ( talk • contribs) 18:24, April 19, 2008
it might be helpful to add a column with a two or three character that indicates whether the device is capable of a duplex connection, whether duplex connection is symmetrical, and an optional footnote.
(footnotes would permit adding info on things like asymmetrical upload/download rates while keeping the table width reasonable.) —Preceding unsigned comment added by 69.253.239.161 ( talk) 18:49, 22 April 2008 (UTC)
![]() | This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |