From owner-freebsd-stable@FreeBSD.ORG Mon Aug 18 22:07:12 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3447AB16 for ; Mon, 18 Aug 2014 22:07:12 +0000 (UTC) Received: from pp2.rice.edu (proofpoint2.mail.rice.edu [128.42.201.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EA5C03CA4 for ; Mon, 18 Aug 2014 22:07:11 +0000 (UTC) Received: from pps.filterd (pp2.rice.edu [127.0.0.1]) by pp2.rice.edu (8.14.5/8.14.5) with SMTP id s7IM79wI008454 for ; Mon, 18 Aug 2014 17:07:09 -0500 Received: from mh1.mail.rice.edu (mh1.mail.rice.edu [128.42.201.20]) by pp2.rice.edu with ESMTP id 1numser7tm-1 for ; Mon, 18 Aug 2014 17:07:09 -0500 X-Virus-Scanned: by amavis-2.7.0 at mh1.mail.rice.edu, auth channel Received: from 108-254-203-201.lightspeed.hstntx.sbcglobal.net (108-254-203-201.lightspeed.hstntx.sbcglobal.net [108.254.203.201]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: alc) by mh1.mail.rice.edu (Postfix) with ESMTPSA id D04AE460148 for ; Mon, 18 Aug 2014 17:07:08 -0500 (CDT) Message-ID: <53F2790C.20703@rice.edu> Date: Mon, 18 Aug 2014 17:07:08 -0500 From: Alan Cox User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: vmdaemon CPU usage and poor performance in 10.0-RELEASE References: <4D557EC7CC2A544AA7C1A3B9CBA2B36726098846B4@exchange03.epbs.com> <20140813152522.GI9400@home.opsec.eu> <4D557EC7CC2A544AA7C1A3B9CBA2B36726098847AF@exchange03.epbs.com> <4D557EC7CC2A544AA7C1A3B9CBA2B3672609BBA3C4@exchange03.epbs.com> <53F24E5B.1010809@rice.edu> <4D557EC7CC2A544AA7C1A3B9CBA2B3672609BBA64F@exchange03.epbs.com> In-Reply-To: <4D557EC7CC2A544AA7C1A3B9CBA2B3672609BBA64F@exchange03.epbs.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=0 kscore.compositescore=0 circleOfTrustscore=0 compositescore=0.713890987064109 urlsuspect_oldscore=0.713890987064109 suspectscore=23 recipient_domain_to_sender_totalscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=1 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=0 rbsscore=0.713890987064109 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1408180249 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: Mon, 18 Aug 2014 22:07:12 -0000 On 08/18/2014 16:29, Polyack, Steve wrote: >> -----Original Message----- >> From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- >> stable@freebsd.org] On Behalf Of Alan Cox >> Sent: Monday, August 18, 2014 3:05 PM >> To: freebsd-stable@freebsd.org >> Subject: Re: vmdaemon CPU usage and poor performance in 10.0-RELEASE >> >> On 08/18/2014 13:42, Polyack, Steve wrote: >>> Excuse my poorly formatted reply at the moment, but this seems to have >> fixed our problems. I'm going to update the bug report with a note. >>> Thanks Alan! >> You're welcome. And, thanks for letting me know of the outcome. >> > Actually, I may have spoken too soon, as it looks like we're seeing vmdaemon tying up the system again: > root 6 100.0 0.0 0 16 - DL Wed04PM 4:37.95 [vmdaemon] > > Is there anything I can check to help narrow down what may be the problem? KTrace/truss on the "process" doesn't give any information, I suppose because it's actually a kernel thread. Can you provide the full output of top? Is there anything unusual about the hardware or software configuration? > For the "patch" we simply stole vm_pageout.c from r265945. > > Steve > >>>> -----Original Message----- >>>> From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- >>>> stable@freebsd.org] On Behalf Of Alan Cox >>>> Sent: Wednesday, August 13, 2014 12:14 PM >>>> To: Polyack, Steve >>>> Cc: Kurt Jaeger; freebsd-stable@freebsd.org >>>> Subject: Re: vmdaemon CPU usage and poor performance in 10.0-RELEASE >>>> >>>> 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. >>>> _______________________________________________ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to "freebsd-stable- >>>> unsubscribe@freebsd.org" >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable- >> unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable- >> unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >