Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a big data file need to write to NFS directory which is mapped under a Windows system. I had 2 different approaches to achieve this.

I wrote (using the “save as” command) from the app directly to NFS. I first wrote to a local drive, then copied the file to NFS directory. I didn't do accurate statics, but it occurs to me approach is definitely faster, and seems I cannot find a reasonable explain for this phenomenon, anyone got any ideas?

Say I have a big file (600 MB), if I directly save it to NFS, it will be slower compared to I first save it to local drive then move the file to NFS, why is that?

share|improve this question

put on hold as unclear what you're asking by Jeff Schaller, Networker, Kusalananda, sam, dhag Jul 22 at 16:57

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question.If this question can be reworded to fit the rules in the help center, please edit the question.

This might depend on both the NFS client and the NFS server. What OS does the client run, and what NFS driver? What about the server? – Gilles Jun 15 '12 at 23:42
I find that I get these slow-downs when writing to "strange" volumes if there is any sort of processing associated with the write. What software are you using to save the file? Perhaps, there is some extra processing involved in save (vs. cp or mv) that is causing issues. – Mike Covington Jun 16 '12 at 5:35

Browse other questions tagged or ask your own question.