At 08:03 PM 6/15/01 -0500, you wrote:
>I am interested in the answers to this myself. I am using NAS storage with
>my DNews server. It certainly appears to be stable, though I am not seeing
>incoming feeds over 100K/S. I have been working on this as a seperate
>issue, but your comments make me consider the possibility of the NAS as a
>botleneck.
>
>My server is a dual P800 running Linux with a 100BaseT connection to a 170G
>Quantum SNAPServer for NAS.
A NAS solution can work, and it can be a bottleneck. In general I would
recommend
organizing it like this if you don't actually need to share the data.
Workarea (local)
xover (local)
history (local)
spool1..n (NAS)
That will work best as all the high speed low latency transfers will be
local and the
bulk storage is remote.
But it can infact work ok with everything remote as long as your system is
properly
configured. For example you probably want the network link working in full
duplex mode
if possible. And the nfs mount point should be configured with write
confirmation disabled
if it's an option (it is on NT I can't recall with NFS)
Anyway, by all means send me the output of:
tellnews stats
tellnews status
tellnews stats_in
And I can give you a rough idea if the disk IO is your problem, in brief
you look for
a busy figure above 90% and a big difference between cpu and elapsed
columns in the
stats output.
But really 100K per second is very slow it's unlikely to be caused by your
system but more
likely the sending end or the wide area network speed.
ChrisP.
