That depends on whether your network is misbehaving in other ways as well. In general, unless you are seeing problems, you can turn it off (set it to zero).

But, you should look into network tuning to reduce latency. The quick network test command is tiny and usually has almost no measurable effect on network speed. There are several causes for high network latency. Think of it like a train that sits in the station too long, waiting for the track to clear, or the cars to fill up. It might be a very fast train once it gets going, but it waits too long to get started.

To reduce the effect of latency (without being a network tuning expert) in Sesame, you might consider using some of the commands that produce more data with fewer commands. For example, in the code above, you are using a lot of XResultSetValue commands, that each return the value of one field. Each of these require a round-trip from the client to the server and back to the client. In many cases, this round trip is only carrying a few bytes of data. Sometimes instead, you might consider using any of the external commands that return data from more than one field at a time, or even more than one record at a time, like XLookupSourceListAll and its ilk.