From owner-freebsd-fs@FreeBSD.ORG Fri Feb 28 19:35:33 2014 Return-Path: Delivered-To: freebsd-fs@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 BB336D59 for ; Fri, 28 Feb 2014 19:35:33 +0000 (UTC) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7732F1E4B for ; Fri, 28 Feb 2014 19:35:33 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6B45B211FD for ; Fri, 28 Feb 2014 14:35:23 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute2.internal (MEProxy); Fri, 28 Feb 2014 14:35:24 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=PcTZHrfN0hmd3YT/8bgafr9E0lg=; b=PfMwR V+18fR0+rQ250ZsadDsSUvN5HaAHcuhLuNtL51JIWdkKiX7l7FstYUnIMgUTogBW QShI1dghZGc1C3nKY6Al78rm2XMyBkwE37fVIiy5G55LvzriY3aeBRERjVV7zzlw 7cHeIOgtMFM8Z3lwJiqtmur1mT1eh1gR7u+zkg= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 8318C11E1EA; Fri, 28 Feb 2014 14:35:23 -0500 (EST) Message-Id: <1393616123.28153.89089441.54713282@webmail.messagingengine.com> X-Sasl-Enc: aA22q/i4qOUOaDqLdgPoFoiEEdZwKPkN2PgEh50quZXs 1393616123 From: Mark Felder To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-4527a23f Subject: Re: ZFS and Wired memory, again Date: Fri, 28 Feb 2014 13:35:23 -0600 In-Reply-To: References: <530F6475.4090508@gmail.com> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 19:35:33 -0000 On Fri, Feb 28, 2014, at 13:11, Adam Vande More wrote: > On Fri, Feb 28, 2014 at 12:53 PM, Anton Sayetsky > wrote: > > > 2014-02-28 20:42 GMT+02:00 Larry Rosenman : > > > On 2014-02-28 12:31, Anton Sayetsky wrote: > > >> > > >> 2014-02-28 13:47 GMT+02:00 Matthias Gamsjager : > > >>>>> > > >>>>> > > >>>> > > >>>> +1 from me, FreeBSD 10, uma=0 > > >>>> > > >>>> 52 processes: 2 running, 49 sleeping, 1 zombie > > >>>> CPU: 0.0% user, 0.0% nice, 0.0% system, 0.4% interrupt, 99.6% idle > > >>>> Mem: 31M Active, 16K Inact, 3352M Wired, 17M Cache, 48M Free > > >>>> ARC: 1838M Total, 110M MFU, 18M MRU, 548K Anon, 1876M Header, 75M > > Other > > >>>> Swap: 4096M Total, 126M Used, 3969M Free, 3% Inuse > > >>>> > > >>>> Machine is plain dead. Running database or squid or anything causes > > >>>> excessive swapping. This is the state when I disabled all payload, > > with > > >>>> everything started swap goes to 500M and machine is burning disks. > > >>>> > > >>> > > >>> I wonder do you use any zfs tuning? Like max arc size? Wonder if > > setting > > >>> that to a reasonable amount would help. > > >> > > >> Please read carefully my first message. No any tuning (configs > > >> posted), and problem is not that ZFS uses big amount of memory. I'm > > >> experiencing exactly one problem - Wired mem is significantly larger > > >> than ARC. > > >> E.g. if my ARC size is 2048M, I'm expecting that Wired will not > > >> consume more than ARC+~150M. > > >> _______________________________________________ > > >> freebsd-fs@freebsd.org mailing list > > >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > > > > > Other pieces of the system used wired memory...... > > > > > > Have you investigated that as well? > > And again - this has detailed explanation in the first letter. In short: > > 1. I've booted the system without any memory hungry services (only > > basic like cron, powerd). Wired is 95M, ARC is 25M. > > 2. Then I started reading ZFS pool (tar cpf /dev/null > > /pool/mountpoint). ARC - 2048M, Wired - ~2800M. > > WTF? Who eats more than 700M of kernel memory? Do you really think > > that powerd or cron can do this? > > > Without question, cron could do it. > I can't see cron using kernel memory; that just doesn't make sense to me. Not even the periodic scripts that cron executes should be able to balloon kernel like that. I think I know what meant to infer though -- that some nonstandard cron script is doing something ugly.