From owner-freebsd-stable@FreeBSD.ORG Sat Apr 25 10:43:42 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 688FEFDE for ; Sat, 25 Apr 2015 10:43:42 +0000 (UTC) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0E1310DC for ; Sat, 25 Apr 2015 10:43:41 +0000 (UTC) Received: by wgin8 with SMTP id n8so73220528wgi.0 for ; Sat, 25 Apr 2015 03:43:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=XlboQ+Yf47WaoavjnfepOA6eb2kv/WP+MYj+QG4qFCo=; b=aIt3paSuW6Vkk3yTveGUAxQr6pLdzeQjldqa7cNElNXd2cBzuauaRDNWYWaPVoLlSm e3QPljtLLYKS0lAQTkdQXbxUOV4PBZWcs+wivZCkPVut76sLKqDWTbQhKymfWUBzb/NK BBaUASEdQb1bQE40GDMrhe9JbjZAPMSNRh0wVFBGnyc/A8211vzbWqRLnxxBHFnNeDyi 8MHLMg6VeXURCuUbpg/p4LEE/CNC4ly6Tb5JjdGuQjaoQOHimC8RMgoxhCnnLZSAfVmX 33SKHMw0ICzPQOt//2HOWezyr7QoFmq/tyIVoN5jECSsuW7UOfjgOwBupAr7zGlqHb7R Pv1A== X-Received: by 10.180.96.200 with SMTP id du8mr4575972wib.54.1429958619556; Sat, 25 Apr 2015 03:43:39 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id i6sm20548890wjf.29.2015.04.25.03.43.38 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Apr 2015 03:43:38 -0700 (PDT) Sender: Baptiste Daroussin Date: Sat, 25 Apr 2015 12:43:36 +0200 From: Baptiste Daroussin To: Dmitry Morozovsky Cc: freebsd-stable@FreeBSD.org Subject: Re: protecting some processes from out-of-swap killer Message-ID: <20150425104336.GD13141@ivaldir.etoilebsd.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rqzD5py0kzyFAOWN" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Apr 2015 10:43:42 -0000 --rqzD5py0kzyFAOWN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 25, 2015 at 01:31:14PM +0300, Dmitry Morozovsky wrote: > Hi there colleagues, >=20 > I have stable/10 on a rather big machine (2*8*2 e5 Xeon, 64G RAM, SAS+SSD= ZFS=20 > raid10+ZIL+L2ARC) acting as a PostgreSQL server.=20 >=20 > To use such a big resource pool that is mostly idle, I'd deployed poudrie= re=20 > there (using tmpfs) too. >=20 > Most times this combination works like a charm: LA could be 60+ and no vi= sual=20 > latency increase on SQL queries. >=20 > However, sometimes postgres processes got killed by 'out of swap space'. = =20 > I suppose the source of problem could be that VSZ size of postgres proces= ses=20 > (8-9 G) is bigger than swap congigured (4G). >=20 > Is there any way to prevent this, besides reallocating space for swap? >=20 > Quick googling does not help, at least I could not find answers relevant= =20 > enough. >=20 > Thanks! protect(1) ? Best regards, Bapt --rqzD5py0kzyFAOWN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlU7b9gACgkQ8kTtMUmk6EyPWgCdG6jHIEs8UyIPhQDJZ0AAMknP 3BQAnivyrsSl79NCoyA4gKNoCOj7NovQ =BDgz -----END PGP SIGNATURE----- --rqzD5py0kzyFAOWN--