[MITgcm-devel] slow CVS server -- heres a very good work-around

[Alistair Adcroft]

I think it is not good practice to use CVS with machine names that we can't
alias later on when it dies (i.e. auden.lcs.mit.edu). Outsiders should only
use mitgcm.org or better yet we should create an alias cvs.mitgcm.org and
point it appropriately. This allows us to make changes without affecting
anyone. Do we have control of mitgcm.org?

BTW, the slow down is because of the CVS-mailman interaction not NFS.

A.
--
Dr Alistair Adcroft            http://www.mit.edu/~adcroft
MIT Climate Modeling Initiative        tel: (617) 253-5938
EAPS 54-1523,  77 Massachusetts Ave,  Cambridge,  MA,  USA

-----Original Message-----
From: mitgcm-devel-bounces at mitgcm.org
[mailto:mitgcm-devel-bounces at mitgcm.org] On Behalf Of Ed Hill
Sent: Wednesday, January 21, 2004 5:28 PM
To: MITgcm-devel
Subject: [MITgcm-devel] slow CVS server -- heres a very good work-around



Hi folks,

Jean-Michel and I just noticed that CVS check-outs from mitgcm.org were
proceeding __very__ slowly.  The reason is that the machine itself is
becoming (on occasion) overloaded.  The best fix for the sort term is to use
the machine that is physically serving up the files as your CVS
server:

  bash:
    export CVSROOT=":ext:YOUR_NAME at auden.lcs.mit.edu:/u/gcmpack"
    export CVS_RSH=ssh

  tcsh/csh:
    setenv CVSROOT ":ext:YOUR_NAME at auden.lcs.mit.edu:/u/gcmpack"
    setenv CVS_RSH ssh

instead of mitgcm.org.  This has the added benefit of reducing NFS network
traffic.

Ed

ps - You may see an appreciable (we saw ~10x) speed increase.


-- 
Edward H. Hill III, PhD
office:  MIT Dept. of EAPS;  Room 54-1424;  77 Massachusetts Ave.
            Cambridge, MA 02139-4307
email:   eh3 at mit.edu,  ed at eh3.com
URL:     http://web.mit.edu/eh3/
phone:   617-253-0098
fax:     617-253-4464