Some days ago I complained about that the backup I make on an NT server
are very very long to do.
This morning, I’m copying a 520 Mb file. The ‘File Operations’
dialog box give me an estimation of 9:23 hours !?!
On the qrtp platform:
The network load is actually about 5% (Tx: 37 kb/s Rx: 27 kb/s) with
some peaks to 19%.
The cpu load average is 8%.
On the NT server:
The network load is about 0%
The cpu load is 1%
What’s the problem?
Thanks,
Alain.
I experience similar slow transfer rates, if I write to the NT server. If I
read from the server, it’s ok.
Markus
“Alain Bonnefoy” <alain.bonnefoy@icbt.com> wrote in message
news:3B8280BC.8A0AA27E@icbt.com…
Some days ago I complained about that the backup I make on an NT server
are very very long to do.
This morning, I’m copying a 520 Mb file. The ‘File Operations’
dialog box give me an estimation of 9:23 hours !?!On the qrtp platform:
The network load is actually about 5% (Tx: 37 kb/s Rx: 27 kb/s) with
some peaks to 19%.
The cpu load average is 8%.On the NT server:
The network load is about 0%
The cpu load is 1%What’s the problem?
Thanks,
Alain.
We’ve seen issues with MS stacks being too agressive
about delayed acks. The next patch has a fs-cifs that
sets TCP_NODELAY to work around this. Does it work better
if you connect to a non MS server?
-seanb
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
: Some days ago I complained about that the backup I make on an NT server
: are very very long to do.
: This morning, I’m copying a 520 Mb file. The ‘File Operations’
: dialog box give me an estimation of 9:23 hours !?!
: On the qrtp platform:
: The network load is actually about 5% (Tx: 37 kb/s Rx: 27 kb/s) with
: some peaks to 19%.
: The cpu load average is 8%.
: On the NT server:
: The network load is about 0%
: The cpu load is 1%
: What’s the problem?
: Thanks,
: Alain.
Sean Boudreau a écrit :
We’ve seen issues with MS stacks being too agressive
about delayed acks. The next patch has a fs-cifs that
sets TCP_NODELAY to work around this. Does it work better
if you connect to a non MS server?-seanb
Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
: Some days ago I complained about that the backup I make on an NT server
: are very very long to do.
: This morning, I’m copying a 520 Mb file. The ‘File Operations’
: dialog box give me an estimation of 9:23 hours !?!: On the qrtp platform:
: The network load is actually about 5% (Tx: 37 kb/s Rx: 27 kb/s) with
: some peaks to 19%.
: The cpu load average is 8%.: On the NT server:
: The network load is about 0%
: The cpu load is 1%: What’s the problem?
: Thanks,
: Alain.
Maybe a little bit better, the file manager gives an estimation of 7 hours to
copy the file on a NT station instead of 9 hours and half on a NT server for
the same file (504 mb).
Alain.
. By ‘non MS server’, I mean something like Linux.
My giess is that an ‘NT server’ and ‘NT station’ share
the same tcpip code.
-seanb
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
: Sean Boudreau a écrit :
:> We’ve seen issues with MS stacks being too agressive
:> about delayed acks. The next patch has a fs-cifs that
:> sets TCP_NODELAY to work around this. Does it work better
:> if you connect to a non MS server?
:>
:> -seanb
:>
:> Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
:> : Some days ago I complained about that the backup I make on an NT server
:> : are very very long to do.
:> : This morning, I’m copying a 520 Mb file. The ‘File Operations’
:> : dialog box give me an estimation of 9:23 hours !?!
:>
:> : On the qrtp platform:
:> : The network load is actually about 5% (Tx: 37 kb/s Rx: 27 kb/s) with
:> : some peaks to 19%.
:> : The cpu load average is 8%.
:>
:> : On the NT server:
:> : The network load is about 0%
:> : The cpu load is 1%
:>
:> : What’s the problem?
:>
:> : Thanks,
:> : Alain.
: Maybe a little bit better, the file manager gives an estimation of 7 hours to
: copy the file on a NT station instead of 9 hours and half on a NT server for
: the same file (504 mb).
: Alain.
Sean Boudreau a écrit :
My giess is that an ‘NT server’ and ‘NT station’ share
the same tcpip code.-seanb
Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
: Sean Boudreau a écrit ::> We’ve seen issues with MS stacks being too agressive
:> about delayed acks. The next patch has a fs-cifs that
:> sets TCP_NODELAY to work around this. Does it work better
:> if you connect to a non MS server?
:
:> -seanb
:
:> Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
:> : Some days ago I complained about that the backup I make on an NT server
:> : are very very long to do.
:> : This morning, I’m copying a 520 Mb file. The ‘File Operations’
:> : dialog box give me an estimation of 9:23 hours !?!
:
:> : On the qrtp platform:
:> : The network load is actually about 5% (Tx: 37 kb/s Rx: 27 kb/s) with
:> : some peaks to 19%.
:> : The cpu load average is 8%.
:
:> : On the NT server:
:> : The network load is about 0%
:> : The cpu load is 1%
:
:> : What’s the problem?
:
:> : Thanks,
:> : Alain.: Maybe a little bit better, the file manager gives an estimation of 7 hours to
: copy the file on a NT station instead of 9 hours and half on a NT server for
: the same file (504 mb).: Alain.
Oups sorry Sean. So, I treid to copy it to a HP UX server running Samba 1.9.18p4
and the file manager gave me an estimation of allmost 3 hours and half for 505 mb.
spin says:
Network en0: 6.35% [Tx: 490 Kb/s Rx: 290 Kb/s]
Regards,
Alain.
Do things like ftp work reasonably? What driver
are you running?
-seanb
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
: Sean Boudreau a écrit :
:> . By ‘non MS server’, I mean something like Linux.
:> My giess is that an ‘NT server’ and ‘NT station’ share
:> the same tcpip code.
:>
:> -seanb
:>
:> Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
:> : Sean Boudreau a écrit :
:>
:> :> We’ve seen issues with MS stacks being too agressive
:> :> about delayed acks. The next patch has a fs-cifs that
:> :> sets TCP_NODELAY to work around this. Does it work better
:> :> if you connect to a non MS server?
:> :>
:> :> -seanb
:> :>
:> :> Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
:> :> : Some days ago I complained about that the backup I make on an NT server
:> :> : are very very long to do.
:> :> : This morning, I’m copying a 520 Mb file. The ‘File Operations’
:> :> : dialog box give me an estimation of 9:23 hours !?!
:> :>
:> :> : On the qrtp platform:
:> :> : The network load is actually about 5% (Tx: 37 kb/s Rx: 27 kb/s) with
:> :> : some peaks to 19%.
:> :> : The cpu load average is 8%.
:> :>
:> :> : On the NT server:
:> :> : The network load is about 0%
:> :> : The cpu load is 1%
:> :>
:> :> : What’s the problem?
:> :>
:> :> : Thanks,
:> :> : Alain.
:>
:> : Maybe a little bit better, the file manager gives an estimation of 7 hours to
:> : copy the file on a NT station instead of 9 hours and half on a NT server for
:> : the same file (504 mb).
:>
:> : Alain.
: Oups sorry Sean. So, I treid to copy it to a HP UX server running Samba 1.9.18p4
: and the file manager gave me an estimation of allmost 3 hours and half for 505 mb.
: spin says:
: Network en0: 6.35% [Tx: 490 Kb/s Rx: 290 Kb/s]
: Regards,
: Alain.
Sean Boudreau a écrit :
Do things like ftp work reasonably? What driver
are you running?-seanb
Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
: Sean Boudreau a écrit ::> >
:> My giess is that an ‘NT server’ and ‘NT station’ share
:> the same tcpip code.
:
:> -seanb
:
:> Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
:> : Sean Boudreau a écrit :
:
:> :> We’ve seen issues with MS stacks being too agressive
:> :> about delayed acks. The next patch has a fs-cifs that
:> :> sets TCP_NODELAY to work around this. Does it work better
:> :> if you connect to a non MS server?
:> :
:> :> -seanb
:> :
:> :> Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
:> :> : Some days ago I complained about that the backup I make on an NT server
:> :> : are very very long to do.
:> :> : This morning, I’m copying a 520 Mb file. The ‘File Operations’
:> :> : dialog box give me an estimation of 9:23 hours !?!
:> :
:> :> : On the qrtp platform:
:> :> : The network load is actually about 5% (Tx: 37 kb/s Rx: 27 kb/s) with
:> :> : some peaks to 19%.
:> :> : The cpu load average is 8%.
:> :
:> :> : On the NT server:
:> :> : The network load is about 0%
:> :> : The cpu load is 1%
:> :
:> :> : What’s the problem?
:> :
:> :> : Thanks,
:> :> : Alain.
:
:> : Maybe a little bit better, the file manager gives an estimation of 7 hours to
:> : copy the file on a NT station instead of 9 hours and half on a NT server for
:> : the same file (504 mb).
:
:> : Alain.: Oups sorry Sean. So, I treid to copy it to a HP UX server running Samba 1.9.18p4
: and the file manager gave me an estimation of allmost 3 hours and half for 505 mb.
: spin says:: Network en0: 6.35% [Tx: 490 Kb/s Rx: 290 Kb/s]
: Regards,
: Alain.
To resume:
My qrtp runs 6.1 version with driver devn-el900 on a 3C905 (on board chip). QRTP is
connected directly to the 100 MB network. NT stations, server and HP-UX server are
connected via a 100/10 MB switch.
To copy a 500 Mbytes file:
With fs-cifs (QRTP to NT): more than 9 hours.
With fs-cifs (QRTP to HPUX running samba 1.9.18p4): allmost 3 hours.
With Samba 2.2.0 (NT from QRTP): 9 minutes. Tx load about 1500 kb/s
With fs-cifs/Samba (cp fs-cifs mount point to /tmp): 1 min 50 sec
With fs-cifs/Samba (cp /tmp fs-cifs mount point): 1 min 50 sec
With ftp (QRTP to NT): less than 7 minutes. Tx load about 1200 kb/s
With ftpd (NT from QRTP): less than 7 minutes.Tx load (on qrtp) about 1200 kb/s.
With ftp/ftpd (get qrtp from qrtp): 1 min 40 sec.
With ftp/ftpd (put qrtp to qrtp): 1 min 40 sec.
Thanks
Alain.