Well, it turns out it was a cable problem. When I changed one of the
machines to Jaguar I also changed it's place in the room and started using a
different wall network socket and cable. Changing cables and wall sockets
reverted tcp performance to the original values. If I simply use a crossover
between the machines I even get Gigabit performance. I guess the weird thing
now is why the lamd mode worked (altough not at high performance) and tcp
would take forever, and that internet access was working ok...
Ricardo
On 05/09/2002 18:00, "lam-request_at_[hidden]" <lam-request_at_[hidden]>
wrote:
> From: Ricardo Fonseca <pcl36688_at_[hidden]>
> Reply-To: lam_at_[hidden]
> Date: Thu, 05 Sep 2002 12:29:51 +0100
> To: <lam_at_[hidden]>
> Subject: Re: LAM: LAM on Mac OS X 10.2 Jaguar
>
> I'm quite sure the issue is related to jaguar (or my machines). For example
> with mpich 1.2.4 (which also doesn't work on my multiple machines under
> jaguar) I had to change the socket buffer size to >= 32 KB to work locally
> (the default was 16). Something in there changed...
>
> Ricardo
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
