How about this? As capacities increase, you're becoming more and more impercise:
The difference between 1 kB and 1 KiB is only 24 bytes or 2.400%, but the difference between 1 MB and 1 MiB is 48,574 kB or 4.858%. The difference between 1 GB and 1 GiB is 73.742 MB or 7.374%. The difference between 1 TB and 1 TiB is 99,512 GB or 9.995%. The difference between 1 PB and 1 PiB is 125.899 TB (12.900%).
Do you really want to be dealing with a minimum of 125.9 TB of ambuguity, when discussing petabytes?
> Only annoying pedants like you who say
Without "annoying pendants" like me, there wouldn't be an Internet for trolls like you to play on.
The world you live in:
Q: What's the propagation delay of signals over Ethernet? A: Hmnn... hard to calculate, because we don't really know the speed of light? - Guess we won't be able to build networks.
Q: Could we land a man on the moon? A: I don't think so. We've only been able to measure the distance from the Earth to the moon with +/- 15% precision. We won't be able to do it.
Here's the important part you were ignoring:
---
Hard drive manufacturer: One GigaByte = 1000 bytes
Wrong. Hard drive manufacturers and everyone else who knows how to use SI prefixes correctly knows that one gigabyte is 1,000,000,000 bytes.
Software/everyone else: One GigaByte = 1024 bytes
Wrong again. If in this case you mean 2^30 bytes, 1 GiB = 1,073,741,824 bytes. What about network people? To them, 1 GB is certainly 1,000,000,000 bytes. Does a 100 Mb/s Ethernet operate at 1,000,000 bits per second (10^6) or is is 1,048,576 (2^20)? More and more people are becoming aware of this issue and moving from the old ambiguous use of prefixes representing powers of ten to represent powers of two to the new more percise and seperate binary SI prefixes. Case in point. Bittorent. Download the client, use it, and you'll notice that bytes, in binary multiples are correctly refered to as KiB, MiB, etc.
Once upon a time, computer professionals noticed that 2^10 was very nearly equal to 1000 and started using the SI prefix "kilo" to mean 1024. That worked well enough for a decade or two because everybody who talked kilobytes knew that the term implied 1024 bytes. But, almost overnight a much more numerous "everybody" bought computers, and the trade computer professionals needed to talk to physicists and engineers and even to ordinary people, most of whom know that a kilometer is 1000 meters and a kilogram is 1000 grams.
Then data storage for gigabytes, and even terabytes, became practical, and the storage devices were not constructed on binary trees, which meant that, for many practical purposes, binary arithmetic was less convenient than decimal arithmetic. The result is that today "everybody" does not "know" what a megabyte is. When discussing computer memory, most manufacturers use megabyte to mean 2^20 = 1 048 576 bytes, but the manufacturers of computer storage devices usually use the term to mean 1 000 000 bytes. Some designers of local area networks have used megabit per second to mean 1 048 576 bit/s, but all telecommunications engineers use it to mean 10^6 bit/s. And if two definitions of the megabyte are not enough, a third megabyte of 1 024 000 bytes is the megabyte used to format the familiar 90 mm (3 1/2 inch), "1.44 MB" diskette. The confusion is real, as is the potential for incompatibility in standards and in implemented systems.
Faced with this reality, the
IEEE Standards Board decided that IEEE standards will use the conventional, internationally adopted, definitions of the SI prefixes. Mega will mean 1 000 000, except that the base-two definition may be used (if such usage is explicitly pointed out on a case-by-case basis) until such time that prefixes for binary multiples are adopted by an appropriate standards body.
In December 1998 the International Electrotechnical Commission (IEC), the leading international organization for worldwide standardization in electrotechnology, approved as an IEC International Standard names and symbols for prefixes for binary multiples for use in the fields of data processing and data transmission.
1 trillion bits is 125 GB, whether you're a hard drive manufacturer or not, as "G" is exactly defined as 10^9. If you're interested in representing this quantity in terms of multiples of 2^(30), as in your 116, 1 trillion bits is more correctly stated as 116.5 GiB, 116.5 gigabinary bytes, or 116.5 gibibytes. See the SI spec on prefixes for binary multiples for more information.
A day after four American private contractors in Iraq were murdered, their bodies burned and publicly dismembered, "Kos" wrote:
"I feel nothing over the death of mercenaries [sic]. They aren't in Iraq because of orders, or because they are there trying to help the people make Iraq a better place. They are there to wage war for profit.
Screw them.
A screenshot of the post in question.
I don't think association with this vicious hate monger is in the Open Source community's best interest. Is it?
I might be good to start by measuring your network's performance, without hard drives or application software in the loop. I'd suggest using IPerf to accomplish this.
If you measure less than expected performance with IPerf, your problem is with your NICs, switch, or drivers. If IPerf reports OK numbers, start looking at Samba and your hard drives.
The bus shouldn't be a problem, because even a lowly 32 bit 33 MHz PCI bus has a theoretical 1.056 Gb/s data rate.
a) There's always a space between the number and the units. b) "M" is mega and "m" is milli. There's nine orders of magnitude difference between to two. c) "per" is expressed with a "/".
Observe Robert Heinlein. He captures these feelings well:
A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.
- Lazarus Long in Time Enough For Love by Robert Heinlein
Slashdot Mirror
Two quick examples of 10GigE adapters that do support operation over multi-mode fiber: Intel Pro/10GbE and Neterion (was S2IO) XframeII.
> Talk about actual practical use
How about this? As capacities increase, you're becoming more and more impercise:
The difference between 1 kB and 1 KiB is only 24 bytes or 2.400%, but the difference between 1 MB and 1 MiB is 48,574 kB or 4.858%. The difference between 1 GB and 1 GiB is 73.742 MB or 7.374%. The difference between 1 TB and 1 TiB is 99,512 GB or 9.995%. The difference between 1 PB and 1 PiB is 125.899 TB (12.900%).
Do you really want to be dealing with a minimum of 125.9 TB of ambuguity, when discussing petabytes?
> Only annoying pedants like you who say
Without "annoying pendants" like me, there wouldn't be an Internet for trolls like you to play on.
The world you live in:
Q: What's the propagation delay of signals over Ethernet?
A: Hmnn... hard to calculate, because we don't really know the speed of light? - Guess we won't be able to build networks.
Q: Could we land a man on the moon?
A: I don't think so. We've only been able to measure the distance from the Earth to the moon with +/- 15% precision. We won't be able to do it.
It's not a question of the giga part, everyone knows the metric system by now (I hope)
Really, do you? Last time I looked, G or giga is defined as exactly 10^9 (1,000,000,000).
Here's the important part you were ignoring:
---
Hard drive manufacturer: One GigaByte = 1000 bytes
Wrong. Hard drive manufacturers and everyone else who knows how to use SI prefixes correctly knows that one gigabyte is 1,000,000,000 bytes.
Software/everyone else: One GigaByte = 1024 bytes
Wrong again. If in this case you mean 2^30 bytes, 1 GiB = 1,073,741,824 bytes. What about network people? To them, 1 GB is certainly 1,000,000,000 bytes. Does a 100 Mb/s Ethernet operate at 1,000,000 bits per second (10^6) or is is 1,048,576 (2^20)? More and more people are becoming aware of this issue and moving from the old ambiguous use of prefixes representing powers of ten to represent powers of two to the new more percise and seperate binary SI prefixes. Case in point. Bittorent. Download the client, use it, and you'll notice that bytes, in binary multiples are correctly refered to as KiB, MiB, etc.
If you had actually read the link I posted on SI prefixes for binary multiples, you might know the following historical context:
In December 1998 the International Electrotechnical Commission (IEC), the leading international organization for worldwide standardization in electrotechnology, approved as an IEC International Standard names and symbols for prefixes for binary multiples for use in the fields of data processing and data transmission.
Where do these people learn their math?
Where did you learn your math? One trillion X is, by definition, a terra X.
See here and here
1 trillion bits is 125 GB, whether you're a hard drive manufacturer or not, as "G" is exactly defined as 10^9. If you're interested in representing this quantity in terms of multiples of 2^(30), as in your 116, 1 trillion bits is more correctly stated as 116.5 GiB, 116.5 gigabinary bytes, or 116.5 gibibytes. See the SI spec on prefixes for binary multiples for more information.
From a Reason article:
A day after four American private contractors in Iraq were murdered, their bodies burned and publicly dismembered, "Kos" wrote: A screenshot of the post in question. I don't think association with this vicious hate monger is in the Open Source community's best interest. Is it?
And these "reports" of campaign HQ shootings: let's see some citations
Here's blog post that cites eight seperate attacks
Pakets per second.
Using IPerf to test your network bandwidth is easy:
[machine1]# iperf -s
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.0 sec 1.10 GBytes 941 Mbits/sec
[machine2]# iperf -c machine1
Client connecting to machine1, TCP port 5001
TCP window size: 16.0 KByte (default)
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.10 GBytes 941 Mbits/sec
This, ~950 Mb/s, is around what you can expect from a 1500 MTU GigE network.
I might be good to start by measuring your network's performance, without hard drives or application software in the loop. I'd suggest using IPerf to accomplish this. If you measure less than expected performance with IPerf, your problem is with your NICs, switch, or drivers. If IPerf reports OK numbers, start looking at Samba and your hard drives. The bus shouldn't be a problem, because even a lowly 32 bit 33 MHz PCI bus has a theoretical 1.056 Gb/s data rate.
This is the second story from Timothy in just a bit more than a week where SI units are used incorrectly. See the previous story.
In this story 15-25 Mb/s is expressed two ways:
1) 15-25Mbps
2) 15-24mbps
Both of these are incorrect. Here's an reference on how to use SI correctly to back me up.
In short:
a) There's always a space between the number and the units.
b) "M" is mega and "m" is milli. There's nine orders of magnitude difference between to two.
c) "per" is expressed with a "/".
Actually... you mean "200 Mb/s":
a) Mega is "M". Milli is "m".
b) There's a space between the number and the units.
c) "Per second" is "/s".
Not really. The top500 list lists LANL's ASCI Q at 20.48 Peak TFLOPS and LLNL's ASCI White at 12.29 Peak TFLOPS.
I'll guess it's from Dam Simmons' Hyperion cantos.
9 was named "Shrike". This beta is "Severn". Both are characters from Hyperion.
In Hyperion, Joseph Severn was a cybrid reconstruction of the deceased 19th-century poet John Keats.
I was redirected to this new number, but wasn't asked for a code when I called it... only the name
of the conference.
I did have to say I was a private investor and give my name and a phone number.
I'm listening to the call now.
"That's why they're"...
oops... here's the correct announcement (June 25th) for the 200GB drive.
Western Digital announced a 200 GB drive on June 17th.
You can do this for free with PVMGmake. I have a HOWTO