Performance issue with copying a file - Aix
This is a discussion on Performance issue with copying a file - Aix ; We're on AIX 5.3 with two virtual servers on the same physical box.
Whenever we copy (rcp or ftp) a 20 Mb file from our Windows client to
a directory on the AIX virtual server it takes about 4-5 seconds.
...
-
Performance issue with copying a file
We're on AIX 5.3 with two virtual servers on the same physical box.
Whenever we copy (rcp or ftp) a 20 Mb file from our Windows client to
a directory on the AIX virtual server it takes about 4-5 seconds.
However, copying the same file from the AIX virtual server to the
Windows client takes about 10 minutes. Any ideas what we should be
looking for?
-
Re: Performance issue with copying a file
On Apr 2, 11:41 pm, Jim wrote:
> We're on AIX 5.3 with two virtual servers on the same physical box.
> Whenever we copy (rcp or ftp) a 20 Mb file from our Windows client to
> a directory on the AIX virtual server it takes about 4-5 seconds.
> However, copying the same file from the AIX virtual server to the
> Windows client takes about 10 minutes. Any ideas what we should be
> looking for?
The Whinedoze client running a virus check on the incoming file?
Who initiates the copy from AIX to W? The server or the client? In
the first place, how does AIX see the client? CIFS? Samba? In the
second, it could be the performance of the client, or network
parameters on the server. Any "traffic shapers" running? Quality of
Service?
-
Re: Performance issue with copying a file
On Apr 3, 5:20*am, "Gerard H. Pille" wrote:
> On Apr 2, 11:41 pm, Jim wrote:
>
> > We're on AIX 5.3 with two virtual servers on the same physical box.
> > Whenever we copy (rcp or ftp) a 20 Mb file from our Windows client to
> > a directory on the AIX virtual server it takes about 4-5 seconds.
> > However, copying the same file from the AIX virtual server to the
> > Windows client takes about 10 minutes. Any ideas what we should be
> > looking for?
>
> The Whinedoze client running a virus check on the incoming file?
>
> Who initiates the copy from AIX to W? * The server or the client? *In
> the first place, how does AIX see the client? *CIFS? *Samba? * In the
> second, it could be the performance of the client, or network
> parameters on the server. * Any "traffic shapers" running? *Quality of
> Service?
Sorry, I didn't define the issue very well. We are opening a command
window on our Windows client. The client has been trusted on the AIX
server. We push a 20Mb file from Windows to AIX and it takes 4
seconds. However, if we pull that same file from AIX to our client it
takes 10 minutes. However, using a CIFS mount point, I can cp the file
from AIX to Windows in 90 seconds.
-
Re: Performance issue with copying a file
On Apr 3, 1:56 pm, Jim wrote:
> On Apr 3, 5:20 am, "Gerard H. Pille" wrote:
>
>
>
>
>
> > On Apr 2, 11:41 pm, Jim wrote:
>
> > > We're on AIX 5.3 with two virtual servers on the same physical box.
> > > Whenever we copy (rcp or ftp) a 20 Mb file from our Windows client to
> > > a directory on the AIX virtual server it takes about 4-5 seconds.
> > > However, copying the same file from the AIX virtual server to the
> > > Windows client takes about 10 minutes. Any ideas what we should be
> > > looking for?
>
> > The Whinedoze client running a virus check on the incoming file?
>
> > Who initiates the copy from AIX to W? The server or the client? In
> > the first place, how does AIX see the client? CIFS? Samba? In the
> > second, it could be the performance of the client, or network
> > parameters on the server. Any "traffic shapers" running? Quality of
> > Service?
>
> Sorry, I didn't define the issue very well. We are opening a command
> window on our Windows client. The client has been trusted on the AIX
> server. We push a 20Mb file from Windows to AIX and it takes 4
> seconds. However, if we pull that same file from AIX to our client it
> takes 10 minutes. However, using a CIFS mount point, I can cp the file
> from AIX to Windows in 90 seconds.- Hide quoted text -
>
> - Show quoted text -
Typically, when we have slow transfer rates from a UNIX to UNIX, it
tends to be the settings on one or both network cards. Example: One
card is set to Auto-Negotiation and somewhere on the network, it
detects a device operating at 10 Mb/half duplex, so the transfer slows
down to the slowest denominator. This can often happen in one
direction and not show as a problem when transferring the other way.
Don't know if that might be the case with a Windows PC as well, but it
could be that the switch you are plugged into or the router involved
is passing the AIX host the wrong details about the connection speed.
Check "smit eadap" and look at the setting for "Media Speed" on your
Ethernet adapter.
Steve
-
Re: Performance issue with copying a file
On Apr 3, 7:56 pm, Jim wrote:
> On Apr 3, 5:20 am, "Gerard H. Pille" wrote:
>
>
>
> > On Apr 2, 11:41 pm, Jim wrote:
>
> > > We're on AIX 5.3 with two virtual servers on the same physical box.
> > > Whenever we copy (rcp or ftp) a 20 Mb file from our Windows client to
> > > a directory on the AIX virtual server it takes about 4-5 seconds.
> > > However, copying the same file from the AIX virtual server to the
> > > Windows client takes about 10 minutes. Any ideas what we should be
> > > looking for?
>
> > The Whinedoze client running a virus check on the incoming file?
>
> > Who initiates the copy from AIX to W? The server or the client? In
> > the first place, how does AIX see the client? CIFS? Samba? In the
> > second, it could be the performance of the client, or network
> > parameters on the server. Any "traffic shapers" running? Quality of
> > Service?
>
> Sorry, I didn't define the issue very well. We are opening a command
> window on our Windows client. The client has been trusted on the AIX
> server. We push a 20Mb file from Windows to AIX and it takes 4
> seconds. However, if we pull that same file from AIX to our client it
> takes 10 minutes. However, using a CIFS mount point, I can cp the file
> from AIX to Windows in 90 seconds.
I don't agree with Steve, unless the CIFS connection would be using
other cards.
If not, we can exclude the network and the PC hardware (could have
been a problem writing to disk).
Remains the client software, virus checking is still a possibility,
if writing to the shared directory would bypass that check.
-
Re: Performance issue with copying a file
Jim wrote:
> We're on AIX 5.3 with two virtual servers on the same physical box.
> Whenever we copy (rcp or ftp) a 20 Mb file from our Windows client to
> a directory on the AIX virtual server it takes about 4-5 seconds.
> However, copying the same file from the AIX virtual server to the
> Windows client takes about 10 minutes. Any ideas what we should be
> looking for?
Have you tried a different protocol or program for the copying? I
noticed that when using Zmodem with Hyperterm on a Windows client the
copying is much faster than when using Procomm Connections.
-
Re: Performance issue with copying a file
On Apr 3, 7:56 pm, Jim wrote:
> However, using a CIFS mount point, I can cp the file
> from AIX to Windows in 90 seconds.
Lucky you, we have serious performance problems using a CIFS mount
point on an AIX 5.2 system. Every action slow as hell, a stat() may
take 2 seconds, and a copying a file to it drowns a processor.
-
Re: Performance issue with copying a file
Gerard H. Pille wrote:
> [...]
> I don't agree with Steve, unless the CIFS connection would be using
> other cards.
>
> If not, we can exclude the network and the PC hardware (could have
> been a problem writing to disk).
Actualy, you can't. When you have a duplex mismatch, the problems are
highly timming-sensitive, to the point of having very different symptoms
for ftp & nfs.
"netstat -v" has most of the answers.
-
Re: Performance issue with copying a file
On Apr 3, 2:49*pm, "steven_nospam at Yahoo! Canada"
wrote:
> On Apr 3, 1:56 pm, Jim wrote:
>
>
>
>
>
> > On Apr 3, 5:20 am, "Gerard H. Pille" wrote:
>
> > > On Apr 2, 11:41 pm, Jim wrote:
>
> > > > We're on AIX 5.3 with two virtual servers on the same physical box.
> > > > Whenever we copy (rcp or ftp) a 20 Mb file from our Windows client to
> > > > a directory on the AIX virtual server it takes about 4-5 seconds.
> > > > However, copying the same file from the AIX virtual server to the
> > > > Windows client takes about 10 minutes. Any ideas what we should be
> > > > looking for?
>
> > > The Whinedoze client running a virus check on the incoming file?
>
> > > Who initiates the copy from AIX to W? * The server or the client? *In
> > > the first place, how does AIX see the client? *CIFS? *Samba? * In the
> > > second, it could be the performance of the client, or network
> > > parameters on the server. * Any "traffic shapers" running? *Quality of
> > > Service?
>
> > Sorry, I didn't define the issue very well. We are opening a command
> > window on our Windows client. The client has been trusted on the AIX
> > server. We push a 20Mb file from Windows to AIX and it takes 4
> > seconds. However, if we pull that same file from AIX to our client it
> > takes 10 minutes. However, using a CIFS mount point, I can cp the file
> > from AIX to Windows in 90 seconds.- Hide quoted text -
>
> > - Show quoted text -
>
> Typically, when we have slow transfer rates from a UNIX to UNIX, it
> tends to be the settings on one or both network cards. Example: One
> card is set to Auto-Negotiation and somewhere on the network, it
> detects a device operating at 10 Mb/half duplex, so the transfer slows
> down to the slowest denominator. This can often happen in one
> direction and not show as a problem when transferring the other way.
>
> Don't know if that might be the case with a Windows PC as well, but it
> could be that the switch you are plugged into or the router involved
> is passing the AIX host the wrong details about the connection speed.
>
> Check "smit eadap" and look at the setting for "Media Speed" on your
> Ethernet adapter.
>
> Steve- Hide quoted text -
>
> - Show quoted text -
Thanks Steve, we finally got someone in our infrastructure group to
spend some time looking into this issue and it turned out to be the
network card. It was set to 100 half when our network standard is 1000
full.