Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Stefan Keller <sfkeller(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
Date: 2012-02-26 22:45:37
Message-ID: CAOR=d=370-h5VNu60Ff2h-qvr6jRRwP6sHbML93-u1qAn1jaug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Feb 26, 2012 at 1:11 PM, Stefan Keller <sfkeller(at)gmail(dot)com> wrote:

> So to me the bottom line is, that PG already has reduced overhead at
> least for issue #2 and perhaps for #4.
> Remain issues of in-memory optimization (#2) and replication (#3)
> together with High Availability to be investigated in PG.

Yeah, the real "problem" pg has to deal with is that it writes to
disk, and expects that to provide durability, while voltdb (Mike's db
project) writes to multiple machines in memory and expects that to be
durable. No way a disk subsystem is gonna compete with an in memory
cluster for performance.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tim Uckun 2012-02-26 22:54:46 A better COPY?
Previous Message Stefan Keller 2012-02-26 20:11:04 Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought