FlexNet Publisher Best Practices in terms of Performance

FlexNet Publisher Best Practices in terms of Performance

The performance metrics of FlexNet Publisher are greatly dependent upon the implementation of licensing and deployment model.(e.g., license workflow, network quality).

The following parameters will affect performance:

· The number of licensed features
· The number of checkouts per unit of time
· The number of features in memory vs. those swapped out
· Number of clients with open job handles
· How many pools are created
· Frequency of heartbeats
· Use of Dup_group
· Use of Linger (when a large number of features linger in a given time span)
· Use of TRL

 

Recommendations for Better Performance

1.USE_SERVER is recommended since it improves performance when a license server is used.
2.For a large number of FlexEnabled applications (hundreds), each of which exchange heartbeat messages with the vendor daemon, the network bandwidth used may become significant. In this case, run the FlexEnabled application and server on the same local area network, and run multiple license servers if required. Users can use a license search path in the LM_LICENSE_FILE environment variable to have effective access to both servers.
Enterprises can experience a performance issue when there is slow network communication or if FlexEnabled clients are using a dial-up link to connect to the network.
3.The vendor daemon has a maximum connection limit approaching 30,000 jobs, although the best practice is to limit total connections to no more than 10,000 jobs in order to ensure sufficient license server performance
4.Poor network communication causes system performance to slow. Slow network communication can also cause a delay in the transmission of heartbeats between license servers.

 

Was this article helpful? Yes No
No ratings
Version history
Revision #:
2 of 2
Last update:
‎May 11, 2021 01:55 AM
Updated by:
 
Contributors