Speed up the performance of your Asset Manager Software Counters' calculation!

"My software counters are slow to calculate"... I hear sometimes this feedback and there are several things to consider that can greatly improve the poerformance of software counters.

Let's try in 6 bullets to define a best practice for SW counters perfromance!


  • Check the size of the amSofInstall table, check if bCompact is enabled with more than 4 millions records;
  1. A technote explains how to convert SW installation from PFIs to bCompact records in AM is available to HP Cutsomer Support.
  2. This decreases dramatically the size of PortfolioItems table (software installation records are only in amSoftinstalls and the Porfolio table, which is central in Asset Manager, will be smaller, which means better performances for the SQL queries used by the different processes).
  • Check the amUseRightCount table is cleaned regularly and the number of records: this is the table stroes the results of the software counters... the good thing is that you can access to the history of your SW counters calculation. The bad thing is that it gets bigger and bigger and need cleaning for old records.
  • Check if the “group by” chosen does not lead to thousands of records creation in amRightUses count for each SW counter calculation: typically, this is a bad idea to have an Office Syd 2007 counters with a group by user when you have 200 000 employees in your company
  1. Best practice: a “view related SW installations” action from the SW counter detail (using a group by cost center for instance. This action is provided with the Asset Manager SAM Best Practice package released in August 2011: the SW counter group by can stay high level (cost center for instance) with the ability, using this "view related SW installations" action to drill down installation by installation.
  • Check how the counters are built… using the wizards or specific queries. If using specific queries: are the used fields indexed? The wizards to build software counters bring optimized queries and offer the ability to have a simple interface (you pick up models that you reconcile, according to a template) for powerful software license compliance reporting.
  • More generally: best practice around SW counter: don’t do everything in the counter, pre-count workflows
  1. For instance: here is how the IBM PVU licensing is managed, a PVU pre-calculation workflow will launch a script, comparing the number of cores of the physical server that hosts IBM applications on virtual instances, compare the numbers, take the smallest and use a script library to map the core factor numbers and assign the points to the installation! This was wise to do this out of the software counter in a performance prospective!
  • How many counter are you using? Do you use efficiently the “group by” or “scope” which would avoid to create hundreds of redundant SW counters

With all this, you will enjoy the value of what software counters bring with the performance of their calculation: by the way, a cost for compliance calculated field as well as red / black color for positive or negative counters in the Windows client come with this August SAM package... enjoy!






Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Showing results for 
Search instead for 
Do you mean 
About the Author
Sr. Product Manager of HP Asset Manager, my 12 year experience in IT Asset Management gives me combined technical skills and business practi...

Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.