🎉 We're happy to announce new public releases! ðŸŽ‰

  • SWAT v1.1r1 - Software tracing solution now supporting more architectures and operating systems - see SWAT Release Notes.
  • TriCore v6.2r2 Inspector v1.0r8 - An automated method for identifying toolset issues in compiled output code.
  • VX-toolset for Arm - v8.0r1 - A certified compiler toolset for safety-critical embedded software development on Arm cores.
Contact us to get access!

FLEXlm: Improve performance when using FLEXlm over a wide-area network

28-Nov-2024

To improve performance, FLEXlm network traffic should be minimized. With the most common uses of FLEXlm, traffic is negligible. In particular, checkout, check-in, 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. It should not be used more than once every 15 minutes and it should be particularly avoided when there are a lot of features or concurrent users, resulting in a large amount of data to transmit; 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).

More resources

Was this answer helpful?