Re: Drive performance bottleneck

2005-02-03 Thread Ian Godin
On Feb 3, 2005, at 9:40 AM, Nuno Silva wrote: Ian Godin wrote: I am trying to get very fast disk drive performance and I am seeing some interesting bottlenecks. We are trying to get 800 MB/sec or more (yes, that is megabytes per second). We are currently using PCI-Express with a 16 drive

Re: Drive performance bottleneck

2005-02-03 Thread Ian Godin
On Feb 2, 2005, at 7:56 PM, Bernd Eckenfels wrote: In article <[EMAIL PROTECTED]> you wrote: Below is an oprofile (truncated) of (the same) dd running on /dev/sdb. do you also have the oprofile of the sg_dd handy? Greetings Bernd Just ran it on the sg_dd (using /dev/sg1): CPU: P4 / Xeon,

Re: Drive performance bottleneck

2005-02-03 Thread Ian Godin
On Feb 2, 2005, at 7:56 PM, Bernd Eckenfels wrote: In article [EMAIL PROTECTED] you wrote: Below is an oprofile (truncated) of (the same) dd running on /dev/sdb. do you also have the oprofile of the sg_dd handy? Greetings Bernd Just ran it on the sg_dd (using /dev/sg1): CPU: P4 / Xeon, speed

Re: Drive performance bottleneck

2005-02-03 Thread Ian Godin
On Feb 3, 2005, at 9:40 AM, Nuno Silva wrote: Ian Godin wrote: I am trying to get very fast disk drive performance and I am seeing some interesting bottlenecks. We are trying to get 800 MB/sec or more (yes, that is megabytes per second). We are currently using PCI-Express with a 16 drive

Drive performance bottleneck

2005-02-02 Thread Ian Godin
ast time I really worked with it (2.2), so any suggestions are appreciated. Ian Godin Senior Software Developer DTS/Lowry Digital Images --- CPU: P4 / Xeon, speed 3402.13 MHz (estimated) Counted GLOBAL_POWER_EVENTS events (time during which processor is not stopped) with a unit mask of 0x01

Drive performance bottleneck

2005-02-02 Thread Ian Godin
worked with it (2.2), so any suggestions are appreciated. Ian Godin Senior Software Developer DTS/Lowry Digital Images --- CPU: P4 / Xeon, speed 3402.13 MHz (estimated) Counted GLOBAL_POWER_EVENTS events (time during which processor is not stopped) with a unit mask of 0x01 (mandatory