T.R | Title | User | Personal Name | Date | Lines |
---|
729.1 | low tcp/ip performance on cluster | TAVEIS::SVI | | Mon Apr 07 1997 05:47 | 14 |
| More information:
We tested the ftp performance between the two cluster nodes and found
that the performance is poor, 8 Kbyte/sec. While, the ftp performance
between each node to another Alpha/NT node that is not part of the
cluster configuration is 800 Kbytes/sec.
It seems to be a tcp/ip performance problem between the two cluster
members. Any ideas ?
Thanks,
Tsvika
|
729.2 | check bindings and driver | DECWET::LEES | Will, NTSG DECwest, Seattle | Mon Apr 07 1997 15:22 | 11 |
| Check the network bindings in case their order may be relevent here.
Second, disable the CFS driver. It is our cluster name redirector. It may be
causing additional overhead in opening connections.
You have eliminated the machines' hardware as the cause by itself by
deinstalling clusters and measuring the performance?
Let us know what you find out.
Will
|
729.3 | Binding problems !!!??? | NETRIX::"[email protected]" | Tsvika Lavie | Tue Apr 08 1997 03:41 | 26 |
| HI Will
> Check the network bindings in case their order may be relevent here.
You are right the problem looks like a binding problem,
The original set up was as follow:
I manually set up the network binding in order to enable TCP/IP only over the
external Network card (the one that connected to the LAN),and
enable binding for NETBUEI only over the privet Network (between the two
Cluster member)
To test the binding issue I changed the binding as follow:
I Enabled the TCP/IP binding over the privet Network and made the
the Backup Server to use the privet line to get to the second member,
by using the HOSTS file.
now the TCP/IP performance looks as expected.
Do you have any explanation for this behavior,
Thanks
Tsvika Lavie
[Posted by WWW Notes gateway]
|
729.4 | Also check IP routing? | DECWET::CAPPELLOF | My other brain is a polymer | Tue Apr 08 1997 20:45 | 21 |
| > manually set up the network binding in order to enable TCP/IP only over the
>external Network card (the one that connected to the LAN),and
>enable binding for NETBUEI only over the privet Network (between the two
>Cluster member)
That should have worked fine. I normally run my office cluster that
way. (TCP/IP on the main network card, NETBEUI on the "private" card.)
I get about 210 KB/sec on a slow ethernet link using FTP. Same results
whether I'm talking to a cluster server or a non-cluster machine.
On ServerA, you might want to try
tracert ServerB
to see if your messages are taking some unecessary hops to get from one
machine to the other.
By the way, the previous suggestion to look at CFS won't help here.
The Cluster client code doesn't get involved with TCP/IP socket
connections used by FTP or NetWorker.
|