Armand,
All of the symptoms you describe line up perfectly with a problem I had
recently when upgrading DB hardware.
Everything ran find until we hit some threshold somewhere at which point
the locks would pile up in the thousands just as you describe, all while we
were not I/O bound.
I was movin
be more interested in the random results from bonnie++ but my real
> world experience tells me that for heavily parallel writes etc a
> RAID-10 will stomp a RAID-6 or RAID-60 on the same number of drives.
>
> On Mon, Mar 4, 2013 at 4:47 PM, Steven Crandell
> wrote:
> > Mark,
&
ite, fsync, close where they were effectively tied.
On Mon, Mar 4, 2013 at 4:17 PM, John Rouillard wrote:
> On Mon, Mar 04, 2013 at 03:54:40PM -0700, Steven Crandell wrote:
> > Here's our hardware break down.
> >
> > The logvg on the new hardware is 30MB/s slower (170 M
Here's our hardware break down.
The logvg on the new hardware is 30MB/s slower (170 MB/s vs 200 MB/s )
than the logvg on the older hardware which was an immediately interesting
difference but we have yet to be able to create a test scenario that
successfully implicates this slower log speed in ou
at 8:41 AM, Craig James wrote:
> On Fri, Mar 1, 2013 at 1:52 AM, Steven Crandell > wrote:
>
>> Recently I moved my ~600G / ~15K TPS database from a
>> 48 core@2.0GHz server with 512GB RAM on 15K RPM disk
>> to a newer server with
>> 64 core@2.2Ghz server with 1T
Recently I moved my ~600G / ~15K TPS database from a
48 core@2.0GHz server with 512GB RAM on 15K RPM disk
to a newer server with
64 core@2.2Ghz server with 1T of RAM on 15K RPM disks
The move was from v9.1.4 to v9.1.8 (eventually also tested with v9.1.4 on
the new hardware) and was done via base b
Also probably some good info to be mined out of postbix.
http://www.zabbix.com/wiki/howto/monitor/db/postbix/monitor_postgres_with_zabbix
On Thu, Sep 6, 2012 at 12:44 PM, Josh Berkus wrote:
> On 9/4/12 12:12 AM, charles_xie wrote:
> > Hi all,
> > i have 5 servers that have been installi
