Ok, bad guess and bad design. Temp files should stay local.
I have a working directory on 4 of my local machines (2 of which are
laptops). The local documents, client, and working projects are setup
to replicate to the file server, data dumpster, and backup device. I
use Windoze Briefcase for the Windows boxes and rdist for the Linux
stuff. All are automatic or cron based. The trick is that I never
edit the files directly on the file server. Edits are always done
locally. Synchronization is always one way, from the local machine,
to the file server, never the other direction. Of course, I'm very
careful to maintain accurate date and time information. While there
was a major learning exercise many years ago, it hasn't failed for
maybe 8 years.
Any particular model number WD NAS box? I think you'll find that your
WD box does NOT cache writes. I need he model number to be sure. Last
time I ran IOZONE on some NAS boxes, it was apparent that there was
plenty of read cache, but writes went straight to the drive. Look on:
<
http://www.smallnetbuilder.com/content/view/85/93/>
for NAS benchmarks and tests on your WD. If you feel ambitious,
compare the results with a "real" server, which uses main memory for
caching both reads and writes. I've replaced several NAS boxes with
Linux servers that simply couldn't keep up with the load (mostly brain
dead applications that scribble all over the server, open huge number
of files, do numerous sync operations for no obvious reason, etc.
Dunno. I was doing SPICE in college in the last 1960's.
My guess is that someone didn't test the hell out of every possible
network configuration or goofed by forcing a temp file to live across
the network.
It could, but how old Switcher CAD (LT Spice)? Probably as old as
Linear Tech which was founded in 1981. As I recall, the IBM PC
arrived in the same year.
Ummm.... Model numbers? Network speeds? Media (CAT5, coax, fiber,
two tin cans and a string)? Gigabit? Number and type of network
boxes located between the WD NAS box and your workstation?