Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YX8ci-0003oh-Q1 for pgsql-performance@arkaria.postgresql.org; Sun, 15 Mar 2015 13:30:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YX8ci-0000XO-3W for pgsql-performance@arkaria.postgresql.org; Sun, 15 Mar 2015 13:30:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YX8ce-0000RX-T6 for pgsql-performance@postgresql.org; Sun, 15 Mar 2015 13:30:28 +0000 Received: from mail-wg0-f44.google.com ([74.125.82.44]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YX8ca-0006Px-Ms for pgsql-performance@postgresql.org; Sun, 15 Mar 2015 13:30:27 +0000 Received: by wgbcc7 with SMTP id cc7so20662825wgb.0 for ; Sun, 15 Mar 2015 06:30:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=vhhlIPuhezamRmFoYQw8vtmT2sn1td1nSR+yoC7un8I=; b=VOdqsLXhmUapygnMYR1XoR5D8R4jO+BVKdqGTzsjeZAi6dOltEvm94O5+/lsIGlesJ OruFIbFi9xwNUdeXnc3VRSSbLPBZmqWrPB8jWHc+CCJ4yCijHZQCe150W87vIJhaL7Hl c+6GJvJKx6HClpiumZKBBWp3uDWfphW7QwqSPOiOnf/+T7BBfwWkHi0MOHyCjZEoA4E5 xLG7ooTXGdy9n9FOEpQeW8olzpSKKdnpzQPMo5zaDzzp6Wf0Kqh/hIECm4W78tfenqkg ucLyVx4V6GaGECd27gvkBtmQPQszXS3QAZ8lbrcRdJ9k1PKpjGY2lXGfrjJ47/bNOBNz 61/w== X-Gm-Message-State: ALoCoQl3+OBDe2U/U+ydNPVlkgkt22mKUA0xmFA+b6s8bBsqdW3oaSb2KBg6elY5D3Y4P5JhpAxA X-Received: by 10.180.108.177 with SMTP id hl17mr154672872wib.35.1426426223049; Sun, 15 Mar 2015 06:30:23 -0700 (PDT) Received: from [10.56.92.182] (tmo-101-187.customers.d1-online.com. [80.187.101.187]) by mx.google.com with ESMTPSA id kr5sm11069147wjc.1.2015.03.15.06.30.21 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 15 Mar 2015 06:30:22 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: MusicBrainz postgres performance issues From: Ilya Kosmodemiansky X-Mailer: iPhone Mail (12B440) In-Reply-To: Date: Sun, 15 Mar 2015 14:30:19 +0100 Cc: Robert Kaye , PostgreSQL Performance Content-Transfer-Encoding: quoted-printable Message-Id: <4CA26C8B-B233-4B57-A236-32B0CD747C08@postgresql-consulting.com> References: <9E71CCBE-4CDF-482E-878D-6C16027B6283@musicbrainz.org> To: Josh Krupka X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org > On Mar 15, 2015, at 13:45, Josh Krupka wrote: > Hmm that's definitely odd that it's swapping since it has plenty of free = memory at the moment. Is it still under heavy load right now? Has the out= put of free consistently looked like that during your trouble times? And it seems better to disable swapiness=20 >=20 --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance