From owner-freebsd-stable@FreeBSD.ORG Wed Aug 13 16:13:38 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D96BDC1 for ; Wed, 13 Aug 2014 16:13:38 +0000 (UTC) Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1A1B72B44 for ; Wed, 13 Aug 2014 16:13:38 +0000 (UTC) Received: by mail-ig0-f180.google.com with SMTP id l13so2214105iga.13 for ; Wed, 13 Aug 2014 09:13:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=GNALyqHvvkegyPZeYmqTKS1qqmTbdR6Zy9PsQIJTjRU=; b=JFPxiY0Xme+uF5WEJbBaVpHoM1YeoNoqjet9th0XDEkRUNsLOIG7SsxHOyOp8iCu2/ IMbA3+L+g+dUJFT6cvvSuuW/NocMGKWh6Y6zFAZ+7LSGbyIunbUTGakTQIMYwICfiOn5 TX/1z6vKxx4by+FJRxgBYX+2i3dJc1Ua3P+BJE90sZGgNQysSOxBiKxkl/ZdWvlc+i3r Yqd1viJAZzG9x2g2Li0OoQX4NO+9DKu2+NLG2rqjUxK9eOdw6sAlzTszkWDrcIrF9rG8 kBOyqutXwVoCWMcNmsCKS5EkaHlr3mLyqU3Z8jNW/ZtDcdX3xDSiwLcBn4B+nc841eXL 1AKw== MIME-Version: 1.0 X-Received: by 10.42.198.75 with SMTP id en11mr7493214icb.7.1407946417541; Wed, 13 Aug 2014 09:13:37 -0700 (PDT) Received: by 10.43.17.196 with HTTP; Wed, 13 Aug 2014 09:13:37 -0700 (PDT) Reply-To: alc@freebsd.org In-Reply-To: <4D557EC7CC2A544AA7C1A3B9CBA2B36726098847AF@exchange03.epbs.com> References: <4D557EC7CC2A544AA7C1A3B9CBA2B36726098846B4@exchange03.epbs.com> <20140813152522.GI9400@home.opsec.eu> <4D557EC7CC2A544AA7C1A3B9CBA2B36726098847AF@exchange03.epbs.com> Date: Wed, 13 Aug 2014 11:13:37 -0500 Message-ID: Subject: Re: vmdaemon CPU usage and poor performance in 10.0-RELEASE From: Alan Cox To: "Polyack, Steve" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Kurt Jaeger , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 16:13:38 -0000 On Wed, Aug 13, 2014 at 10:42 AM, Polyack, Steve < Steve.Polyack@intermedix.com> wrote: > > > -----Original Message----- > > From: Kurt Jaeger [mailto:lists@opsec.eu] > > Sent: Wednesday, August 13, 2014 11:25 AM > > > > Hi! > > > > > We have a handful of database servers running FreeBSD 10.0-RELEASE > > > and PostgreSQL 9.3.4. The servers have 128GB or 256GB of RAM. > > > > Are you aware of the recent work on that topic ? > > > > https://www.freebsd.org/news/status/report-2014-04-2014- > > 06.html#PostgreSQL-Performance-Improvements > > > > Maybe kib@ knows more about this ? > > > > I've recently read over this and some other posts, but they all seem to > center around poor postgres performance. In our case at least, some light > to medium usage of postgres generally makes the entire system unusable. > > The patches & documents linked there also all seem to be for -CURRENT, > which we aren't running. We're not too keen on the idea of using CURRENT > in production, either. We're planning on testing 10-STABLE, but I was just > hoping to gain some insight into what the problem may be and whether recent > commits to vmdaemon code in the -STABLE tree may have a positive effect on > what we've seen. > > There is a good chance that your problem is fixed by r265945.