#1489 optimize REST Key searches for performance on large Key repos
Closed: migrated 3 years ago by dmoluguw. Opened 8 years ago by vakwetu.

Right now, the Key interface uses a simple search (with specific time and entry limits) to
list keys. There are basically four types of searches:
1. clientID = X
2. status = Y
3. clientID =X and status =Y
4. no params specified. Becomes (serialno=*)

Searches of type (1) and (3) can only be optimized by indexing the attributes - which has already been done.

Search 4 is the same as an existing VLV search - and is needed for better performance in a UI. Right now this isn't an issue because the new key types are not accessible via the UI in any case. It corresponds to key-find with no search args. We should change the code to actually use this VLV search in this case.

Search 2 could be optimized by creating VLV indexes for specific status values (and then using VLV code).

Proposed Milestone:
10.3


Per CS/DS meeting of 07/20/2015: 10.3

Metadata Update from @vakwetu:
- Issue set to the milestone: UNTRIAGED

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2048

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata