Bug 1372748

Summary:	[RFE] Improve Performance of Compliance Call
Product:	[Community] Candlepin	Reporter:	smcdowel
Component:	candlepin	Assignee:	candlepin-bugs
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.9.51	CC:	khowell, nmoumoul, redakkan, tdeanton, tpfromme
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-04 10:29:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description smcdowel 2016-09-02 14:35:02 UTC

With the new RHSM Web System Lists, we are exposing the System Status (Properly Subscribed, Partially Subscribed, etc.) for each system. While this is a very welcome enhancement for our customers, it comes with a performance cost, due to the compliance call (/consumers/compliance) we make to generate those statuses. We would like to explore options for improving this performance.

Along with better performance of the call itself, we would like to see compliantUntil added to the compliance response.  To get it out of the API, we need to construct our queries like this:

"/consumers/compliance?uuid=0cb583db-d949-4316-a37f-adbab3ff2132&uuid=e3013ff8-9ff5-42cf-8d6b-c68cc4d3e076&include=0cb583db-d949-4316-a37f-adbab3ff2132.compliantUntil&include=e3013ff8-9ff5-42cf-8d6b-c68cc4d3e076.compliantUntil&"

This is a query with two consumers. In order to avoid exceeding the maximum length of a url, RHSM must retrieve compliance data 50 consumers at a time. Ideally we should be able to retrieve the data in larger batches.


Version-Release number of selected component (if applicable): 0.9.51, 2.0

Comment 7 Nikos Moumoulidis 2022-03-04 10:29:29 UTC

This bug quite old now. We've have some other bzs to improve performance already, some already in flight, such as:
https://bugzilla.redhat.com/show_bug.cgi?id=2059131
https://bugzilla.redhat.com/show_bug.cgi?id=2044944
https://bugzilla.redhat.com/show_bug.cgi?id=1991960

And given that we don't plan on adding any features for Entitlement-based workflows, in favor of investing in SCA-based ones, we do not plan to add the proposed features here.