NFS Performance issue against NetApp

Marc G. Fournier scrappy at hub.org
Fri May 3 20:29:23 UTC 2013


On 2013-05-02, at 17:39 , Adam McDougall <mcdouga9 at egr.msu.edu> 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 … there are no other temp files that I'm aware of … 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 …





More information about the freebsd-fs mailing list