Oh brother..
asked and answered..
"Each vendor will have to be asked what method they use in the real world."
The answer is "ask them.."
Subject Closed.
-----Original Message----- From: Jay Orr [SMTP:orrjl@stl.nexen.com] Sent: Friday, March 31, 2000 7:30 AM To: Paquette, Trevor Cc: Karl Swartz; toasters@mathworks.com Subject: RE: benchmark
Yes, and THAT WAS MY ORIGINAL QUESTION THAT YOU RESPONDED TO - what do Netapps and Sun do?
On Thu, 30 Mar 2000, Paquette, Trevor wrote:
Each vendor either sticks with powers of 2 (as they should) or they
round
it. Each vendor will have to be asked what method they use in the real
world.
Yes, we all know the theory, but I'm talking real world. As the thread reads, some vendors use 1000 KB = 1MB, while some don't. I am asking what is implemented. Do the majority of the unix vendors adhere
to
the proper base 2 theory of metrics or do they use base 10 combos (i.e. the 1GB = 1000 MB)?
On Thu, 30 Mar 2000, Paquette, Trevor wrote:
Here we go..
A bit is the smallest unit of data in a computer; has a single
binary
value
of either 0 or 1 A byte is a unit of information that is eight bits long. (half a
byte,
or 4
bits is called a nibble)
Computer storage is measured in byte multiples; which are based on
powers of
Because humans deal mainly with the decimal system, the resulting
number
is
usually 'rounded off' for humans to better comprehend.
1 Kbyte = 1024 bytes = 2^10 bytes = 1,024
bytes
1 Megabyte = 1024 Kbytes = 2^20 bytes = 1,048,576
bytes
1 Gigabyte = 1024 Mbytes = 2^30 bytes = 1,073,741,824
bytes
1 Terabyte = 1024 Gbytes = 2^40 bytes = 1,099,511,627,776
bytes
1 Petabyte = 1024 Tbytes = 2^50 bytes = 1,125,899,906,842,624
bytes
1 Exabyte = 1024 Pbytes = 2^60 bytes = 1,152,921,504,606,846,976
bytes
= approx. 1 billion GB
Humm... Fun.. Do you know off hand how Solaris and netapp defines
a MB
or
GB? In moving around files I started thinking about this, since
depending
on what tool you use you get file sizes in "bytes" "kbytes" "MB"
or
"GB"
(a la gnu df, solaris df, etc...)
On Wed, 29 Mar 2000, Karl Swartz wrote:
> Uh, if I can ask a simple (stupid?) question - I was looking
at
the
source
> code for postmark and noticed this : > > #define KILOBYTE 1024 > #define MEGABYTE (1000*KILOBYTE) > > Isn't a megabite 1024*1024?
It depends on who you ask. Long ago, disk vendors decided that
they
could make their disks look bigger if they defined MB to be 2000 sectors (assuming 512 byte sectors, or 8000 sectors for 128 byte sectors), and GB became 1000 MB. Of course they also talked
about
unformatted capacity to further inflate the size over reality.
In a similar vein, telco people talk about 1K = 1000. The 64K
B-
channel in an ISDN line is 64000 bits per second, not 65536.
I'm not sure about networking, but I think FDDI and 100base-T
both
have a data rate of 100 * 10^6 bits/second, not 100 * 2^20.
(Not to
be
confused with the signalling rate, which as I recall is 125 *
10^6
for
FDDI with some flavor of 4/5 encoding, and possibly something
similar
for 100base-T.)
What's right for Postmark? Good question. It looks like Jeff
picked
the standard for disk sizes, but it's not clear that's the
standard
most applicable to this case. Aren't standards wonderful? :-)
-- Karl Swartz Network Appliance Engineering Work: kls@netapp.com http://www.netapp.com/ Home: kls@chicago.com http://www.chicago.com/~kls/
Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO
Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO
Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO
By restating someone's question as an answer, it is not "asked and answered". I had put to this forum the question of what does Netapps and Sun do, since there are many Netapp people on this and many people who use Sun here.
Your answers have been less then helpful - If you don't know then why did you reply to the original posting? It was a SIMPLE QUESTION, I didn't ask for the theory of powers of two, I didn't ask "who should I ask", I didn't say "how does Trevor feel about this?" I simply posted to this informative list a simple question of WHAT DOES NETAPP and SUN do in formulating what they consider MB and GB.
Please, if you have nothing useful to add to a discussion, don't interject. That's just common decency...
On Fri, 31 Mar 2000, Paquette, Trevor wrote:
Oh brother..
asked and answered..
"Each vendor will have to be asked what method they use in the real world."
The answer is "ask them.."
Subject Closed.
-----Original Message----- From: Jay Orr [SMTP:orrjl@stl.nexen.com] Sent: Friday, March 31, 2000 7:30 AM To: Paquette, Trevor Cc: Karl Swartz; toasters@mathworks.com Subject: RE: benchmark
Yes, and THAT WAS MY ORIGINAL QUESTION THAT YOU RESPONDED TO - what do Netapps and Sun do?
On Thu, 30 Mar 2000, Paquette, Trevor wrote:
Each vendor either sticks with powers of 2 (as they should) or they
round
it. Each vendor will have to be asked what method they use in the real
world.
Yes, we all know the theory, but I'm talking real world. As the thread reads, some vendors use 1000 KB = 1MB, while some don't. I am asking what is implemented. Do the majority of the unix vendors adhere
to
the proper base 2 theory of metrics or do they use base 10 combos (i.e. the 1GB = 1000 MB)?
On Thu, 30 Mar 2000, Paquette, Trevor wrote:
Here we go..
A bit is the smallest unit of data in a computer; has a single
binary
value
of either 0 or 1 A byte is a unit of information that is eight bits long. (half a
byte,
or 4
bits is called a nibble)
Computer storage is measured in byte multiples; which are based on
powers of
Because humans deal mainly with the decimal system, the resulting
number
is
usually 'rounded off' for humans to better comprehend.
1 Kbyte = 1024 bytes = 2^10 bytes = 1,024
bytes
1 Megabyte = 1024 Kbytes = 2^20 bytes = 1,048,576
bytes
1 Gigabyte = 1024 Mbytes = 2^30 bytes = 1,073,741,824
bytes
1 Terabyte = 1024 Gbytes = 2^40 bytes = 1,099,511,627,776
bytes
1 Petabyte = 1024 Tbytes = 2^50 bytes = 1,125,899,906,842,624
bytes
1 Exabyte = 1024 Pbytes = 2^60 bytes = 1,152,921,504,606,846,976
bytes
= approx. 1 billion GB
Humm... Fun.. Do you know off hand how Solaris and netapp defines
a MB
or
GB? In moving around files I started thinking about this, since
depending
on what tool you use you get file sizes in "bytes" "kbytes" "MB"
or
"GB"
(a la gnu df, solaris df, etc...)
On Wed, 29 Mar 2000, Karl Swartz wrote:
> > Uh, if I can ask a simple (stupid?) question - I was looking
at
the
source > > code for postmark and noticed this : > > > > #define KILOBYTE 1024 > > #define MEGABYTE (1000*KILOBYTE) > > > > Isn't a megabite 1024*1024? > > It depends on who you ask. Long ago, disk vendors decided that
they
> could make their disks look bigger if they defined MB to be 2000 > sectors (assuming 512 byte sectors, or 8000 sectors for 128 byte > sectors), and GB became 1000 MB. Of course they also talked
about
> unformatted capacity to further inflate the size over reality. > > In a similar vein, telco people talk about 1K = 1000. The 64K
B-
> channel in an ISDN line is 64000 bits per second, not 65536. > > I'm not sure about networking, but I think FDDI and 100base-T
both
> have a data rate of 100 * 10^6 bits/second, not 100 * 2^20.
(Not to
be
> confused with the signalling rate, which as I recall is 125 *
10^6
for
> FDDI with some flavor of 4/5 encoding, and possibly something
similar
> for 100base-T.) > > What's right for Postmark? Good question. It looks like Jeff
picked
> the standard for disk sizes, but it's not clear that's the
standard
> most applicable to this case. Aren't standards wonderful? :-) > > -- > Karl Swartz Network Appliance Engineering > Work: kls@netapp.com http://www.netapp.com/ > Home: kls@chicago.com http://www.chicago.com/~kls/ >
Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO
Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO
Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO
----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO
Actually Trevor answered the question (and I don't mean to start a flame war here). You need to check on each vendor's page. By each vendor I mean disk vendor (seagate, IBM, quantum, etc.), because they differ. Also the problem becomes that some vendors embraced 2^10 factor and then changed to the 10^3 factor. For example, the drive specs that I have seen from quantum and seagate use the 10^3 factor for MB and GB, I'm not sure what other vendors use.
Sometimes the simple questions don't have simple answers.
Jay Orr wrote:
By restating someone's question as an answer, it is not "asked and answered". I had put to this forum the question of what does Netapps and Sun do, since there are many Netapp people on this and many people who use Sun here.
Your answers have been less then helpful - If you don't know then why did you reply to the original posting? It was a SIMPLE QUESTION, I didn't ask for the theory of powers of two, I didn't ask "who should I ask", I didn't say "how does Trevor feel about this?" I simply posted to this informative list a simple question of WHAT DOES NETAPP and SUN do in formulating what they consider MB and GB.
Please, if you have nothing useful to add to a discussion, don't interject. That's just common decency...
On Fri, 31 Mar 2000, Paquette, Trevor wrote:
Oh brother..
asked and answered..
"Each vendor will have to be asked what method they use in the real world."
The answer is "ask them.."
Subject Closed.
--<snip>
If we were buying direct from Seagate, IBM, quantum, etc, then I agree that would be the proper thing to do. However many of us buy from Sun and Netapp, and those were the vendors in question here; as there are Netapp folks here and experienced Sun folk here as well, I believe this to be an aprropriate forum for the specific question asked previously. Which I will now reiterate: Does anyone know whether Sun and Netapp follow the 2^10 or 10^3 convention when stating the size of the disks they resell?
Justin
John Tatar wrote:
Actually Trevor answered the question (and I don't mean to start a flame war here). You need to check on each vendor's page. By each vendor I mean disk vendor (seagate, IBM, quantum, etc.), because they differ. Also the problem becomes that some vendors embraced 2^10 factor and then changed to the 10^3 factor. For example, the drive specs that I have seen from quantum and seagate use the 10^3 factor for MB and GB, I'm not sure what other vendors use.
Sometimes the simple questions don't have simple answers.
Jay Orr wrote:
By restating someone's question as an answer, it is not "asked and answered". I had put to this forum the question of what does Netapps and Sun do, since there are many Netapp people on this and many people who use Sun here.
Your answers have been less then helpful - If you don't know then why did you reply to the original posting? It was a SIMPLE QUESTION, I didn't ask for the theory of powers of two, I didn't ask "who should I ask", I didn't say "how does Trevor feel about this?" I simply posted to this informative list a simple question of WHAT DOES NETAPP and SUN do in formulating what they consider MB and GB.
Please, if you have nothing useful to add to a discussion, don't interject. That's just common decency...
On Fri, 31 Mar 2000, Paquette, Trevor wrote:
Oh brother..
asked and answered..
"Each vendor will have to be asked what method they use in the real world."
The answer is "ask them.."
Subject Closed.
--<snip>
=================================================================== John J. Tatar Systems & Network Engineering Section Advanced Computer Applications Group Decision & Information Sciences Division Argonne National Laboratory mailto:tatar@dis.anl.gov or john@tatar.com Office: 630-252-3242 Fax: 630-252-5128 -----BEGIN PGP PUBLIC KEY BLOCK----- Version: PGP 6.5.2
mQCNAziz6CMCWAEEAOyFiK5GI2DgmY9ykjaXORSqOngRPiVoeSzGAceY86rKGiIX D9ZK1103tS56qOZWuhRDhmkXd2oaHOb2ZiO6FgdVf6S+s3wlzHRhKV8Jj0VBiPDu 9ypIrQqDGRLezQhVrVg/Jbmnvg2tYd9uVyTchcLGd0ArmQBoC3buEtJ0xfQJAAUR tCFKb2huIEouIFRhdGFyIDx0YXRhckBkaXMuYW5sLmdvdj6JAJUDBRA4s+gjdu4S 0nTF9AkBAbYDA/9S5Lh38UfuBa97mg5642u9tR0Y3gcKE6bBZLuCciI+2kjaDzzP fFT8Xw2ArpbQRKlX0RQnrm5tEaB0Fb6iZY1xcFvaHIMqJY7jP/Tb7NfMUtJqlo8t PLOMVdVt61o9DEOrVC8XheG4Qrt0eWuQSUMtu+H3udVBhLgewFkupXZ4PQ== =n8Dq
-----END PGP PUBLIC KEY BLOCK-----