Skip to content

[runwhen-local-feedback] investigate process delays with cq #706

@stewartshea

Description

@stewartshea

Observation
It's unclear if this is related to the amount of resources that are available for discovery, but we need to investigate performance issues where CQ is taking VERY long (like, 40 minutes), or it causes the container to restart.

Possible Suggestions
Investigate whether we are indexing everything first and then filtering the output (if so, can we pre-filter?). If not, find the root cause of the identified performance issues.

Any other details or context
Are there any other metrics we can expose for total scan duration?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions