Network
Helix server can run over any TCP/IP network. For remote users or distributed configurations, Perforce offers options like proxies and the commit/edge architecture that can enhance performance over a WAN. Compression in the network layer can also help.
Helix server
uses a TCP/IP connection for each client interaction with the server. The
server’s port address is defined by P4PORT
, but the TCP/IP
implementation picks a client port number. After the command completes
and the connection is closed, the port is left in TIME_WAIT
state for two minutes. Although the port number ranges from
1025
to 32767
, generally only a few hundred or
thousand can be in use simultaneously. It is therefore possible to occupy
all available ports by invoking a
Helix server
command many times in rapid succession, such as with a script.
TCP keepalive
By default, keepalives are enabled if that functionality is supported by the OS. If your network silently drops idle connections, users might experience unexpected connectivity issues. The following p4 server configurables override the behavior configured in the operating system:
For a general explanation of keepalive technology, see:
http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html
http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/usingkeepalive.html
Your search for returned result(s).