Date: Thu, 5 Dec 2013 16:52:46 +0100
From: Andres Freund <andres@2ndquadrant.com>
To: Metin Doslu <metin@citusdata.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>,
 pgsql-hackers <pgsql-hackers@postgresql.org>,
 Amit Kapila <amit.kapila16@gmail.com>,
 Claudio Freire <klaussfreire@gmail.com>
Subject: Re: [HACKERS] Parallel Select query performance and shared buffers
Message-ID: <20131205155246.GB3866@alap2.anarazel.de>
References: 
 <CAL1dPcfZJFO2gr+53mU14VrrHxT-Bs6QOYgzQNV_VgxnkKUaZA@mail.gmail.com>
 <CAL1dPcdm1q0q0VtOpe2gfOyCwS7FkzURw=ZQ1RsLgfKgz5=gMg@mail.gmail.com>
 <20131204182601.GF7383@awork2.anarazel.de>
 <CAL1dPce25L_X2a_QebJyC4rHhmYVaR8xQBud0y799opY9JKqpw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAL1dPce25L_X2a_QebJyC4rHhmYVaR8xQBud0y799opY9JKqpw@mail.gmail.com>
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 2013-12-05 17:46:44 +0200, Metin Doslu wrote:
> I tried your patches on next link. As you suspect I didn't see any
> improvements. I tested it on PostgreSQL 9.2 Stable.

You tested the correct branch, right? Which commit does "git rev-parse
HEAD" show?

But generally, as long as your profile hides all the important
information behind the hypervisor's cost, you're going to have a hard
time analyzing the problems. You really should try to reproduce the
problems on native hardware (as similar to the host hardware as
possible), to get accurate data. On CPU bound workloads that information
is often transportable to the virtual world.

Greetings,

Andres Freund

-- 
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


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