From owner-freebsd-fs@FreeBSD.ORG Fri May 3 21:01:46 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 25709DDE for ; Fri, 3 May 2013 21:01:45 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-ve0-x22b.google.com (mail-ve0-x22b.google.com [IPv6:2607:f8b0:400c:c01::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 6E2271469 for ; Fri, 3 May 2013 21:01:45 +0000 (UTC) Received: by mail-ve0-f171.google.com with SMTP id oy12so1893997veb.2 for ; Fri, 03 May 2013 14:01:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=JbJonByzZkXJ3CADhWRAbUJF/u0slQDAJWPiGJNdMHo=; b=Lix34C5su0yOLlL7uX8Njuj6utVq+KhXfQDzc/TVcJOUXBLdKg7+pTy2TkC3xeblHY UpeQeYmxX9c9ZoQQG/K1TmYnn8Cw7d5I+PywuIc2EGWfL/ptF8HxcC0T58yyBR3cKT77 VAMX5VsVx3tLu44oIEXsN3Eq8gGI8prUBEaGC3K0dltHeAMgFjE0Ljx/Fq3uN95sjoNI zr7qHw1Srv7fFjFg5W11bXshZF8amfUArFYQlW4QPSUfBMT4BtE5XkEHqlzO+T+WQ5aF MTEoCj73BvFSa4EijIeLo42YN3+y7HnWbN/9jKgMn1Ywxfa5npQhri3A+C4M96YwHG6N P43A== MIME-Version: 1.0 X-Received: by 10.52.176.65 with SMTP id cg1mr3592704vdc.1.1367614904954; Fri, 03 May 2013 14:01:44 -0700 (PDT) Received: by 10.58.208.166 with HTTP; Fri, 3 May 2013 14:01:44 -0700 (PDT) In-Reply-To: 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> Date: Fri, 3 May 2013 16:01:44 -0500 Message-ID: Subject: Re: NFS Performance issue against NetApp From: Chuck Burns To: "Marc G. Fournier" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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 21:01:46 -0000 So, wait.. you're comparing a jail-over-nfs to.. what? linux doesnt have jails, so you aren't really making a fair comparison here. On Fri, May 3, 2013 at 3:29 PM, Marc G. Fournier wrote: > > 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. I= f > 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 wou= ld > 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, s= o > moving pieces of it to local drives isn't particularly feasible =85 > > > > _______________________________________________ > 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" >