Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-performance-owner+M54296=pgsql-performance-ar@postgresql.org>)
	id 1bT1bf-0003uG-83
	for pgsql-performance@arkaria.postgresql.org; Fri, 29 Jul 2016 06:49:17 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-performance-owner+M54296=pgsql-performance-ar@postgresql.org>)
	id 1bT1be-00052B-RF
	for pgsql-performance@arkaria.postgresql.org; Fri, 29 Jul 2016 06:49:14 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <trafdev@mail.ru>)
	id 1bT1Zz-0002wQ-DC
	for pgsql-performance@postgresql.org; Fri, 29 Jul 2016 06:47:31 +0000
Received: from smtp53.i.mail.ru ([94.100.177.113])
	by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.84_2)
	(envelope-from <trafdev@mail.ru>)
	id 1bT1Zw-0006OD-Mp
	for pgsql-performance@postgresql.org; Fri, 29 Jul 2016 06:47:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru;
 s=mail2;
	h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:Cc:References:Subject:To:From;
 bh=+i7+Kjr1dw3AzpoHi+xX2DtuWxri1IAHp7/cv4bkAno=;
	b=Ilifk6FS7k0tXmt0sAZ6u961t9ZCjaQaLH0Eqbi3vePADtZvR0RhVcwquTqhS4mi68Y9RCf0aIYwcm6bWbiUpANIY9tnhMJtO/Gu6c4tiieLWzao8xa8Nj/ZmoWn6oALb57v9FVHe5p8DQ2NQuJDV//3Nnc9zvz7YT2OneHD3tE=;
Received: from c-50-156-112-176.hsd1.ca.comcast.net ([50.156.112.176]:39986
 helo=[192.168.1.116])
	by smtp53.i.mail.ru with esmtpa (envelope-from <trafdev@mail.ru>)
	id 1bT1Zu-0002Q2-Qx; Fri, 29 Jul 2016 09:47:27 +0300
From: trafdev <trafdev@mail.ru>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Subject: Re: PostgreSQL on ZFS: performance tuning
References: <1cdf08f7-de8f-c55f-c1ec-29a5f15d5011@mail.ru>
 <c3e5970c-312f-2c98-c3a7-b3273f1d7c07@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Message-ID: <70bfa668-8904-8668-d0a6-6a6e27d38245@mail.ru>
Date: Thu, 28 Jul 2016 23:47:22 -0700
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <c3e5970c-312f-2c98-c3a7-b3273f1d7c07@2ndquadrant.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailru-Sender: 
 CF8F31C009940187A7F35C43154C059F63E47CF4EF85F36D537619A92B49C5409CECCB7664E4AB27EC456C66D2279EA7
X-Mras: OK
X-Pg-Spam-Score: -2.7 (--)
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@postgresql.org>
List-Post: <mailto:pgsql-performance@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-performance>
List-Unsubscribe: 
 <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
X-Mailing-List: pgsql-performance
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

> > - from what I can see, Postgres uses memory too carefully. I would like
> > somehow to force it to keep accessed data in memory as long as possible.
> > Instead I often see that even frequently accessed data is pushed out of
> > memory cache for no apparent reasons.
> >
>
> This is probably a consequence of the primarycache misconfiguration.

Thanks! And I'm using "primarycache=all" in my deployment...


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