Skip site navigation (1) Skip section navigation (2)

Re: H800 + md1200 Performance problem

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
Cc: Cesar Martin <cmartinp(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: H800 + md1200 Performance problem
Date: 2012-04-16 17:47:52
Message-ID: CAOR=d=3CqHTYQeNn-yCNDZyj+YEGZ-xKkhhPHihX_+O8GG2qFQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Mon, Apr 16, 2012 at 10:31 AM, Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk> wrote:
>> From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
>>On Mon, Apr 16, 2012 at 8:13 AM, Cesar Martin <cmartinp(at)gmail(dot)com> wrote:
>>> Hi,
>>>
>>> Finally the problem was BIOS configuration. DBPM had was set to "Active
>>> Power Controller" I changed this to "Max
>>> Performance". http://en.community.dell.com/techcenter/power-cooling/w/wiki/best-practices-in-power-management.aspx
>>> Now wirite speed are 550MB/s and read 1,1GB/s.
>>
>>Why in the world would a server be delivered to a customer with such a
>>setting turned on?  ugh.
>
>
> Because it's Dell and that's what they do.
>
>
> When our R910s arrived, despite them knowing what we were using them for, they'd installed the memory to use only one channel per cpu. Burried deep in their manual I discovered that they called this "power optimised" mode and I had to buy a whole extra bunch of risers to be able to use all of the channels properly.
>
> If it wasn't for proper load testing, and Greg Smiths stream scaling tests I don't think I'd even have spotted it.

See and that's where a small technically knowledgeable supplier is so
great.  "No you don't want 8 8G dimms, you want 16 4G dimms." etc.

In response to

pgsql-performance by date

Next:From: Merlin MoncureDate: 2012-04-16 19:38:10
Subject: Re: SeqScan with full text search
Previous:From: Glyn AstillDate: 2012-04-16 16:31:47
Subject: Re: H800 + md1200 Performance problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group