IBM Support

How much of my system's resources will the TEM Client use?

Technote (troubleshooting)


Problem(Abstract)

The TEM Client was designed to work silently and efficiently in the background and not bother the user at the computer or any other application.

Resolving the problem

The TEM Client was designed to work silently and efficiently in the background and not bother the user at the computer or any other application.

The TEM Client can be installed on any computer that meets the OS requirement. The hardware requirements for the Client are very low and it will function properly with as low as 64 MB of RAM and a 200 mhz processor.

The TEM Client is in a constant loop of evaluating each Fixlet message, Task, Baseline, etc. to see if it is relevant. If the client notices anything new, it immediately sends its results to the TEM Server. This allows the Console users to see an up to date view of the vulnerabilities and computer properties in the network.

The TEM Client is engineered with performance and efficiency as a primary goal and has many different optimizations built-in to make it fast and use a negligible amount of resources.

Here are some key points regarding the TEM Client's resource usage:

  • The TEM Client is tuned to take <1% of the CPU usage at any given time. The target CPU usage is adjustable as a configuration option (although the default settings are expected to be appropriate for almost all cases).
  • Occasionally, the TEM Client CPU will spike a few percent higher during a refresh, gather, or action, but the spike will be brief (mostly less than 1-2 seconds).
  • You can verify the TEM Client resource usage behavior by looking at a process viewing tool such as the Windows Task Manager on a computer with the Client installed. The BESClient.exe process CPU should hover around 0-2% depending on the speed of the computer and the TEM Client CPU time / Total CPU time should be <1%.
  • The memory usage of the TEM Client will fluctuate depending on exactly what the TEM Client is doing at that moment and the configuration of each deployment, but will normally stay around 4-12 MB.
  • The TEM Client utilizes a sophisticated, patented caching scheme known as "fingerprinting" that allows it not to waste time re-checking certain computer attributes that have not changed since the last evaluation
  • The resource usage of the TEM Client will remain relatively constant even if you have many different Fixlet sites (but it will take slightly longer for the TEM Client to complete a loop of evaluating all of the Fixlet messages).
  • The amount of space the TEM Client uses varies significantly depending on how many Fixlet sites are subscribed and how many actions have been run. A typical TEM Client will use about 15-70 MB of disk space. The program files for TEM are approximately 5 MB uncompressed and each Fixlet site will use some more disk space.
  • The TEM Client will routinely read bytes from disk, but due to the optimizations in the TEM Client, OS, and hardware, most of the information will be cached causing the actual hard disk usage caused by the TEM Client to be very small.
  • The TEM Client runs as the SYSTEM account on Windows computers and root on Unix/Linux computers giving it complete access to the computer.
  • Many of the TEM Client's performance characteristics can be tuned using information at https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Endpoint%20Manager/page/Configuration%20Settings.
  • The TEM Client only gathers differences when gathering new Fixlets or actions instead of re-gathering all information. When reporting the TEM Client only reports information not previously reported to the TEM Server instead of re-reporting all information. These optimizations allow the Client to operate with negligible network impact, which is usually around 25-100 KB of network usage spread throughout a day. (Of course, sending out actions such patches or application deployments will cause more network traffic.)
  • Note that you can optionally put the TEM Client into "sleep mode" so that it does not use any CPU for parts of the day.

Historical Number

43

Document information

More support for: IBM BigFix family

Software version: Version Independent

Operating system(s): Platform Independent

Reference #: 1505815

Modified date: 10 October 2014


Translate this page: