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
Any particular model number WD NAS box? I think you'll find that your
Dunno. I was doing SPICE in college in the last 1960's.That's why I was hoping LTSpice was post 1980
It could, but how old Switcher CAD (LT Spice)? Probably as old as
Ummm.... Model numbers? Network speeds? Media (CAT5, coax, fiber,
It's the Western Digital WD5000G031. CAT-5 wiring in home run method,On Sat, 20 Sep 2008 12:54:45 -0700, Joerg
notthisjoergsch@removethispacbell.net> wrote:
It was pointed to the local hard disk. But it still writes the *.raw
files to wherever the sim files are.
Ok, bad guess and bad design. Temp files should stay local.
So now I ferried those to the local
HD, violating a ground rule here. In the evening I must ferry all this
back. T'is the rule, to make sure client files are clearly separated.
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.
It's Linux and it does cache. Not much to set there, it's a Western
digital box with only a miniscule amount of control valves. Basically
you can set some permissions, that's pretty much it.
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.
That's why I was hoping LTSpice was post 1980
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 store an image in RAM and then do all the fast stuff from
there. But no ...
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.
It's a regular Ethernet (wired) LAN. SMC Barricade router, Western
Digital MyBook World with a LAN port, right next to that router.
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?
Nope.
Yes, it is slow. I knew that before I bought it but that is of no
Well, I don't have a Linux machine. But it's ok, when there is some time
USB flash drives are freaking slow :-(
I'll live with it for now. If I move the *asc. files to the PC before
But then why doesn't it keep that whole 100MB raw data file all in RAM?
Nothing found with that number with Google or on the WDC search page.
What model SMC? Sorry to be so obnoxious about extracting the exact
Yeah, building temp files over the LAN is not a great idea. If your
No videos, photos, games, archived applications, disk images, CD and
Good, fast, cheap... pick two.
It should work (famous last words).
SMC 7008 BR. It never had any performance or reliability issues. Jim
Well, I run backups and stuff during lunch and dinner time. Or I just
I use the PC only as a tool. Just like pliers, wrenches and stuff. Fun
Let's put it that way, good and cheap is good enough for me and my
Last words in the west: "Hey y'all, watch this now!"
Good idea, I'll do that. But I don't want to sound like a complainer.
This brings up an interesting alternative. I used to be able to"Frank Buss" <fb@frank-buss.de> wrote in message
news:1529ejbweq35j$.1xwgvwd3lxcbr$.dlg@40tude.net...
For Windows
XP there is no built-in program available.
This reflects the fact that Windows uses a *huge* disk cache by default
(hundreds of megabytes if no other program requests the memory!), and the
folks at Microsoft seemed to equate using a RAM disk to "I want really fast
performance" (as opposed to Joerg's "I don't want my mechanical hard drive
grinding"), which a huge cache provides, so this is why they make you go to
some effort to get a "real" RAM disk.
Or at least that's my interpretation of events.
No such luck. Spice that would run on a PC is only since 1985On Sat, 20 Sep 2008 12:54:45 -0700, Joerg
notthisjoergsch@removethispacbell.net> wrote:
It was pointed to the local hard disk. But it still writes the *.raw
files to wherever the sim files are.
Ok, bad guess and bad design. Temp files should stay local.
So now I ferried those to the local
HD, violating a ground rule here. In the evening I must ferry all this
back. T'is the rule, to make sure client files are clearly separated.
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.
It's Linux and it does cache. Not much to set there, it's a Western
digital box with only a miniscule amount of control valves. Basically
you can set some permissions, that's pretty much it.
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.
That's why I was hoping LTSpice was post 1980
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 store an image in RAM and then do all the fast stuff from
there. But no ...
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.