We used the enterprise test suite, which works with large numbers of files in different directories. The number and frequency of files accessed make it unlikely that a client would be able to satisfy a majority of requests from cache. WebBench 3.0 was used to test the software's ability to handle client HTTP requests through their respective Web servers. In all cases, the servers were configured using the default settings and bundled applications were installed and running, although they were not doing any actual work. The client must issue a Read for the file, but any changes only occur in the client's local cache.
Problems happen when the same workstation opens a file with Op-locks enabled, then reopens it.
Specifically, the server considers the second opening to be a unique session and informs the client to clear its Op-locks. When that happens the client clears the lock on the wrong task and its connection is timed out. Opportunistic locking affects performance, as local Write operations are faster than equivalent operations over the network.