- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Forum
- :
- Number of Threads for FNMS Agent
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a user group that is extremely concerned about any potential impact of the FNMS agent on their application. Can someone verify that the Linux agent is single-threaded? This would prevent the agent from ever using more than one CPU core. In my testing I only see one thread, but I'm hoping for a definitive answer. We are currently using the 2019 R2 agent, but will be upgrading to 2021 R1.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The main processes in the FlexNet inventory agent itself are single threaded. However I couldn't guarantee that that other processes that do work as a result of agent activity (that is, running executables that are not part of the agent itself) aren't multi-threaded.
However probably more relevant to this is that the main agent processes, and child processes they invoke, are (by default) run with a low CPU priority. So if there are other processes running that want to use CPU resources, they will typically get priority ahead of the agent processes (according to the operating system's CPU scheduling behaviors).
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The main processes in the FlexNet inventory agent itself are single threaded. However I couldn't guarantee that that other processes that do work as a result of agent activity (that is, running executables that are not part of the agent itself) aren't multi-threaded.
However probably more relevant to this is that the main agent processes, and child processes they invoke, are (by default) run with a low CPU priority. So if there are other processes running that want to use CPU resources, they will typically get priority ahead of the agent processes (according to the operating system's CPU scheduling behaviors).
