Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-09 Thread Merlin Moncure
On 11/8/06, Spiegelberg, Greg [EMAIL PROTECTED] wrote: Merlin, I'm kinda shocked you had such a bad exp. with the AMS200. We have a unit here hooked up to a 4-node Linux cluster with 4 databases banging on it and we get good, consistent perfomance out of it. All 4 nodes can throw 25 to 75

Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-08 Thread Markus Schaber
Hi, Brian, Brian Hurt wrote: So the question is: is there an easy to install and run, read-heavy benchmark out there that I can wave at them to get them to fix the problem? For sequential read performance, use dd. Most variants of dd I've seen output some timing information, and if not, do a

Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-08 Thread Merlin Moncure
On 11/8/06, Markus Schaber [EMAIL PROTECTED] wrote: Hi, Brian, Brian Hurt wrote: So the question is: is there an easy to install and run, read-heavy benchmark out there that I can wave at them to get them to fix the problem? For sequential read performance, use dd. Most variants of dd I've

Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-08 Thread Cosimo Streppone
Merlin Moncure wrote: On 11/8/06, Markus Schaber [EMAIL PROTECTED] wrote: Hi, Brian, Brian Hurt wrote: So the question is: is there an easy to install and run, read-heavy benchmark out there that I can wave at them to get them to fix the problem? For sequential read performance, use dd.

Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-08 Thread Luke Lonergan
Similar experiences with HP and their SmartArray 5i controller on Linux. The answer was: this controller has won awards for performance! It can't be slow!, so we made them test it in their own labs an prove just how awfully slow it was. In the case of the 5i, it became apparent that HP had no

Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-07 Thread Dimitri Fontaine
Hi, Le lundi 6 novembre 2006 21:47, Brian Hurt a écrit : So the question is: is there an easy to install and run, read-heavy benchmark out there that I can wave at them to get them to fix the problem? I have a second database running on a single SATA drive, so I can use that as a comparison

[PERFORM] Easy read-heavy benchmark kicking around?

2006-11-06 Thread Brian Hurt
I'm having a spot of problem with out storage device vendor. Read performance (as measured by both bonnie++ and hdparm -t) is abysmal (~14Mbyte/sec), and we're trying to get them to fix it. Unfortunately, they're using the fact that bonnie++ is an open source benchmark to weasle out of doing

Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-06 Thread Luke Lonergan
, November 06, 2006 03:49 PM Eastern Standard Time To: pgsql-performance@postgresql.org Subject:[PERFORM] Easy read-heavy benchmark kicking around? I'm having a spot of problem with out storage device vendor. Read performance (as measured by both bonnie++ and hdparm -t) is abysmal

Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-06 Thread Merlin Moncure
On 11/6/06, Brian Hurt [EMAIL PROTECTED] wrote: I'm having a spot of problem with out storage device vendor. Read performance (as measured by both bonnie++ and hdparm -t) is abysmal (~14Mbyte/sec), and we're trying to get them to fix it. Unfortunately, they're using the fact that bonnie++ is

Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-06 Thread Scott Marlowe
On Mon, 2006-11-06 at 15:09, Merlin Moncure wrote: On 11/6/06, Brian Hurt [EMAIL PROTECTED] wrote: I'm having a spot of problem with out storage device vendor. Read performance (as measured by both bonnie++ and hdparm -t) is abysmal (~14Mbyte/sec), and we're trying to get them to fix it.

Re: [PERFORM] Easy read-heavy benchmark kicking around?

2006-11-06 Thread Mark Kirkwood
Brian Hurt wrote: I'm having a spot of problem with out storage device vendor. Read performance (as measured by both bonnie++ and hdparm -t) is abysmal (~14Mbyte/sec), and we're trying to get them to fix it. Unfortunately, they're using the fact that bonnie++ is an open source benchmark to