From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 19 14:46:11 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D6D210656C7 for ; Tue, 19 Jan 2010 14:46:11 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-qy0-f174.google.com (mail-qy0-f174.google.com [209.85.221.174]) by mx1.freebsd.org (Postfix) with ESMTP id F0D8C8FC1D for ; Tue, 19 Jan 2010 14:46:10 +0000 (UTC) Received: by qyk4 with SMTP id 4so2353539qyk.7 for ; Tue, 19 Jan 2010 06:46:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=DS5Xbcr8saUcIy5U5DP6bUJJZV2BiPc/98tVNBNE0yA=; b=Sande7/L8eESF10MKSmEWpTHRwQA2q3r6xoEgdfYurlRaPlJaLvEFaLGi8FM8Mi8X+ wFJHfk9PsOuWLFY8PmsgAAF844U/H+1Z7wQ4F6+RhEWHw3D+fcq9rGK+fqssWMtqzidx 27yIZoN1tGcKVZITPj3ZbUNlkp9kxwqP2S1Wc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=AQJXYSRzhQI/VqpUHYfnTusapFbNOOMRm6EhVWJHsXeiOCecmvJ1J3uSw/2zuYt8cE WH53kEXS8hRciMaMOMAdAg8/zK+poLE55foUDhDwkvRP461b60OjMmeYv1zGFGlsOgeP GXKoBDWpvfxi74YWyUtWoYdXEHQ3GaL0su82I= Received: by 10.224.13.145 with SMTP id c17mr3081633qaa.244.1263912366483; Tue, 19 Jan 2010 06:46:06 -0800 (PST) Received: from ?192.168.31.4? (ppp-22.65.dialinfree.com [209.172.22.65]) by mx.google.com with ESMTPS id 23sm6128109qyk.3.2010.01.19.06.46.02 (version=SSLv3 cipher=RC4-MD5); Tue, 19 Jan 2010 06:46:04 -0800 (PST) Sender: "J. Hellenthal" Message-ID: <4B55C5A6.2020109@DataIX.net> Date: Tue, 19 Jan 2010 09:45:58 -0500 From: jhell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <7f14551c1001190119x46c6b04dx2362cd1252f0d81@mail.gmail.com> <7f14551c1001190216w49814186n1ada2b721380502b@mail.gmail.com> In-Reply-To: <7f14551c1001190216w49814186n1ada2b721380502b@mail.gmail.com> X-Enigmail-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Setting "zfs_arc_max" value in FreeBSD 8. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2010 14:46:11 -0000 On 1/19/2010 5:16 AM, Sherin George wrote: > Thanks Ivan :) > > I found It. add following in /boot/loader.conf > > =================== > vfs.zfs.arc_max="10244M" > =================== > > -- > Best Regards, > Sherin > > On Tue, Jan 19, 2010 at 3:15 PM, Ivan Voras wrote: > >> On 01/19/10 10:19, Sherin George wrote: >> >>> Hello, >>> >>> I am trying to tune ZFS file system by setting "zfs_arc_max" value in >>> FreeBSD 8. >>> >>> In solaris, it is achieved like this >>> >>> ================================================= >>> For example, if an application needs 5 GBytes of memory on a system with >>> 36-GBytes of memory, you could set the arc maximum to 30 GBytes, >>> (0x780000000 or 32212254720 bytes). Set the zfs:zfs_arc_max parameter in >>> the >>> /etc/system file: >>> >>> set zfs:zfs_arc_max = 0x780000000 >>> >>> or >>> >>> set zfs:zfs_arc_max = 32212254720 >>> ================================================= >>> >>> But, I couldn't find /etc/system file in FreeBSD. >>> >>> Could some one please guide me to correctly configure "zfs_arc_max" in >>> FreeBSD 8. >>> >> >> You should probably start here: >> >> http://wiki.freebsd.org/ZFSTuningGuide >> >> and more generally, here: >> >> http://wiki.freebsd.org/ZFS >> I just thought I would give a shout at this for stable/7 as of last week. I am not sure if this is just me but I had tried to adjust zfs_arc_max and found out that it was unadjusted to my value after the system came back up. Anyone know if it is adjustable on a system with 1024MB of ram ? Is this just being auto calculated by some other value ? -- jhell