Message-ID: <5293AE2E.5020405@archidevsys.co.nz>
Date: Tue, 26 Nov 2013 09:08:14 +1300
From: Gavin Flower <GavinFlower@archidevsys.co.nz>
Organization: ArchiDevSys
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Lee Nguyen <leemobile@gmail.com>, pgsql-performance@postgresql.org
Subject: Re: Postgresql in a Virtual Machine
References: 
 <CAHghi5Cj_6KmwaUopF3y=vSjs3Q83VyXQy5DQhfLyP_Zt0yxbA@mail.gmail.com>
In-Reply-To: 
 <CAHghi5Cj_6KmwaUopF3y=vSjs3Q83VyXQy5DQhfLyP_Zt0yxbA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 26/11/13 09:01, Lee Nguyen wrote:
> Hi,
>
> Having attended a few PGCons, I've always heard the remark from a few 
> presenters and attendees that Postgres shouldn't be run inside a VM. 
> That bare metal is the only way to go.
>
> Here at work we were entertaining the idea of running our Postgres 
> database on our VM farm alongside our application vm's.  We are 
> planning to run a few Postgres synchronous replication nodes.
>
> Why shouldn't we run Postgres in a VM?  What are the downsides? Does 
> anyone have any metrics or benchmarks with the latest Postgres?
>
> Thanks!
>
> Lee Nguyen
I suspect that it is a performance and reliability issue that affects 
any ACID database.

AFAIK, in a VM there is less certainty as to when a disk I/O is actually 
complete and safely on the disk.

I think vm's are probably fine for testing, but not for production.


Cheers,
Gavin


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance