Performance

• Performance factors

• Connections per process

• Locking

Performance factors

A number of factors might affect the apparent performance of the VisionFS server.

• The theoretical maximum bandwidth for standard Ethernet traffic is 1Mbyte/second (10Mbps).

• In practice, the real speed is dependent on the speed of the client and the speed of the UNIX file system. If NFS is also involved (for example, a shared folder might access a directory mounted over NFS) speeds will reduce further.

• VisionFS does not buffer data. However, both UNIX and Windows do.

Connections per process

Each VisionFS process on the UNIX server can handle a number of connections from Windows clients, up to a maximum. Once the maximum is exceeded, a new process starts. Only one connection can be attended to in each process at a time.

By changing the maximum number of connections per process, you can trade off response time against resource usage. More connections per process makes more efficient use of server resources, but might result in decreased performance for users. Fewer connections per process increases performance for users, but uses server resources less efficiently.

See also:

• ``Optimizing process usage'' in the Windows Help index

Locking

Two changes can improve the performance of the VisionFS server:

• If a share gives access to a CD-ROM drive, then no files will ever be modified, so you can turn off locking completely for that share.

• If you are sure that files in a share won't be edited by UNIX users as well as Windows users, then turn on opportunistic locking in that share.