Why am I getting Global Collection CPU threshold exceeded alerts in SPECTRUM?

book

Article ID: 51970

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

Why am I getting Global Collection CPU threshold exceeded alerts in SPECTRUM?

Cause

This can be caused by excessive "NOT" statements in the Global Collection Search criteria. The way the "NOT" criteria works is less efficient and creates higher load in processing than the other statements do. This is because first, SPECTRUM searches the database and collects ALL objects relevant for evaluation of the criteria (whether they are = or not =), then it identifies the objects within that group that meet the EQUAL  criteria, and finally, it subtracts those identified meeting the EQUAL criteria from the ALL collection of objects to get the "NOT  = " objects.

This can also be caused by excessive use of external attributes in the search criteria. External attributes take longer to retrieve.

Environment

Release: Any
Component:

Resolution

Avoid using the NOT comparison if possible. Also, use INTERNAL attributes whenever available.