Hi,
I was using Postmark to measure NFS performance in Solaris <-> NetApp configuration. Very good tool, I think.
http://www.netapp.com/tech_library/3022.html http://www.netapp.com/tech_library/postmark.html
I even ported it to Windows NT :) But, I think there should be something more Windows-native. I just want to measure remote disk performance, NFS or CIFS connected. NetBench seems to be to compicated...
Any suggestions?
Thank you.
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?
On Wed, 29 Mar 2000, Rainchik, Aleksandr (MED, Non GE) wrote:
Hi,
I was using Postmark to measure NFS performance in Solaris <-> NetApp configuration. Very good tool, I think.
http://www.netapp.com/tech_library/3022.html http://www.netapp.com/tech_library/postmark.html
I even ported it to Windows NT :) But, I think there should be something more Windows-native. I just want to measure remote disk performance, NFS or CIFS connected. NetBench seems to be to compicated...
Any suggestions?
Thank you.
----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO
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/
Does anyone know of a library or set of utilities for Unix [commercial/free] that lets you add/remove users from NT4 global groups? Such would allow me to move a Web application from a NT Web server to my Unix/Apache/NetApp Web server.
Thanks!
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
-
James N. Maze -
Jay Orr -
kls＠netapp.com -
Mitch Wright -
Rainchik, Aleksandr (MED, Non GE)