We e using FLEXlm over a wide-area network. What can we do to improve performance?
FLEXlm network traffic should be minimized. With the most common uses of FLEXlm, traffic is negligible. In particular, checkout, checkin, and heartbeats use very little networking traffic. There are two items, however, which can send considerably more data and should be avoided or used sparingly: • lmstat -a should be used sparingly. lmstat -a should not be used more than, say, once every 15 minutes, and should be particularly avoided when there’s a lot of features, or concurrent users, and therefore a lot of data to transmit; say, more than 20 concurrent users or features. • Prior to FLEXlm v5, the port@host mode of the LM_LICENSE_FILE environment variable should be avoided, especially when the license file has many features, or there are a lot of license files included in LM_LICENSE_FILE. The license file information is sent via the network, and can place a heavy load. Failures due to port@host will generate the error LM_SERVNOREADLIC (-61). D.
FLEXlm network traffic should be minimized. With the most common uses of FLEXlm, traffic is negligible. In particular, checkout, checkin and heartbeats use very little networking traffic. There are two items, however, which can send considerably more data and should be avoided or used sparingly: • `lmstat -a’ should be used sparingly. lmstat -a should not be used more than, say, once every 15 minutes, and should be particularly avoided when there’s a lot of features, or concurrent users, and therefore a lot of data to transmit; say, more than 20 concurrent users or features. • prior to FLEXlm v5, the `port@host’ mode of the LM_LICENSE_FILE environment variable should be avoided, especially when the license file has a lot of features, or there are a lot of license files included in $LM_LICENSE_FILE. The license file information is sent via the network, and can place a heavy load. Failures due to `port@host’ will generate the lm_errno LM_SERVNOREADLIC (-61).
