From owner-freebsd-fs@FreeBSD.ORG Fri May 3 20:29:23 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0C433A5E for ; Fri, 3 May 2013 20:29:23 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id CDACA1238 for ; Fri, 3 May 2013 20:29:22 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.189]) by hub.org (Postfix) with ESMTP id DDB161A45917; Fri, 3 May 2013 17:29:15 -0300 (ADT) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.189]) (amavisd-maia, port 10024) with ESMTP id 41172-10; Fri, 3 May 2013 20:29:15 +0000 (UTC) Received: from [10.5.250.150] (remote.ilcs.sd63.bc.ca [142.31.148.2]) by hub.org (Postfix) with ESMTPA id 2B16F1A45916; Fri, 3 May 2013 17:29:15 -0300 (ADT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: NFS Performance issue against NetApp From: "Marc G. Fournier" In-Reply-To: <5183074B.5090004@egr.msu.edu> Date: Fri, 3 May 2013 13:29:13 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <834305228.13772274.1367527941142.JavaMail.root@k-state.edu> <75CB6F1E-385D-4E51-876E-7BB8D7140263@hub.org> <20130502221857.GJ32659@physics.umn.edu> <420165EE-BBBF-4E97-B476-58FFE55A52AA@hub.org> <5183074B.5090004@egr.msu.edu> To: Adam McDougall X-Mailer: Apple Mail (2.1503) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2013 20:29:23 -0000 On 2013-05-02, at 17:39 , Adam McDougall wrote: > My understanding of jboss is it unpacks your war files (or whatever) = to a temp deploy dir but essentially tries to run everything from = memory. If you replaced a war file, it would usually undeploy and = redeploy. Is your jboss extracting the archives to an NFS dir or can = you reconfigure or symlink it to extract to a local temp dir when = starting up? I can't imagine offhand why it might be useful to store = the temp dir on NFS. I would think most of the writes at startup would = be to temp files that would be of no use after the jboss java process is = stopped. Unless I've missed something, jboss extracts the war when you do the = deploy, so subsequent restarts just use the extracted files and = shouldn't be slowed down by those writes =85 there are no other temp = files that I'm aware of =85 but, in this case, the problem is that we're = running jboss within a jail'd environment, and the jail is sitting on = the NFS server, so moving pieces of it to local drives isn't = particularly feasible =85