High CPU Utilization on Inventory Central Server 16 Release 6

Comments

16 comments

  • Curtis Hendzell

    Having the exact same issue since the 16.6 upgrade.

    0
    Comment actions Permalink
  • Anthony Weiss

    I have a case open, no engagement on it since yesterday. Just pinged sales to see what is going on. Will update thread with resolution if one is found.

    Glad to know I have company at least.

    0
    Comment actions Permalink
  • Jason Seiberlich

    Same here.

    0
    Comment actions Permalink
  • Anthony Weiss

    @Jason & @Curtis_Hendzell Did you guys open cases as well? Where are you in your case if so?

    0
    Comment actions Permalink
  • Jason Seiberlich

    No I have not, but I can if you think it will speed things along. So slow even just scanning.

    0
    Comment actions Permalink
  • Jason Seiberlich

    I have a support ticket in now.

    0
    Comment actions Permalink
  • Anthony Weiss

    Support had me send DB over to them, they report it is being forwarded to development.

    0
    Comment actions Permalink
  • Jason Seiberlich

    Same here

    0
    Comment actions Permalink
  • Jason Seiberlich

    They asked if I had rebooted the server PDQ was installed on. I had already rebooted once but did it again and seems to have helped. CPU usage has been between 0% and up to 30% when scanning a large number.

    0
    Comment actions Permalink
  • Anthony Weiss

    Any other changes?

    0
    Comment actions Permalink
  • Jason Seiberlich

    They had me turn off "heartbeat" and then do a scan but it didn't change anything

    0
    Comment actions Permalink
  • Jason Seiberlich

    They had me install an update (16.6.0.2). Seems ok so far.

    0
    Comment actions Permalink
  • Anthony Weiss

    Just received the same update myself. Definitely helps the situation, but still very CPU intensive.

    0
    Comment actions Permalink
  • Jason Seiberlich

    My CPU usage stays around 0%-5% only jumps momentarily when doing a large scan, so mine seems good to go.

    0
    Comment actions Permalink
  • Erling Johansen

    They send me 16.6.0.8, but still 99-100% CPU utilization. They asked for the DB and it has been forwarded to development.

    0
    Comment actions Permalink
  • Anthony Weiss

    I am running same as you, but no CPU issues. Support did review my DB and provided guidance on performance improvements:

    Last, if you have any collections using the "member of collection" filter, let's change that to its more reliable filter-cousin "computer collection is member" instead. Development has been able to find a performance issue that is directly related to using that particular filter.

    Not totally sure why this is not a little more publicized, but sounds like a good way to improve performance. I have a ton of these in my environment that I am starting to remediate.

    From Ticket #154507

    One of our clever guys here wrote a SQL report to find filters which might need changing:

    Select Collections.Name as "Collection", reportdefinitionfilters.Value as "Filtering for this Collection" from Collections join reportdefinitionfilters on Collections.ReportDefinitionId = reportdefinitionfilters.ReportDefinitionId where reportdefinitionfilters.tablename = 'Collection'

    0
    Comment actions Permalink

Please sign in to leave a comment.