CRL publishing needs performance review.
CRL split times for adding 50K to existing 50K entries: Operation Time in ms ================================================ Copying delta CRL cache: 8 ------------------------------------------------ Preparing data for delta CRL generation: 2 Signing and encoding delta CRL: 99 Storing delta CRL: 253 Delta CRL publishing: 2150 ------------------------------------------------ Preparing data for CRL generation: 31 Adding extensions: 0 Signing and encoding CRL: 77 Storing CRL: 688 Publishing CRL: 2945 ------------------------------------------------ Delta CRL total: 2504 CRL total: 3749 Total: 6253 ================================================
[[BR]]
From mach1: ---------------------------------------------------------------- Issuing point CRL numbers Number of entries Recent changes MasterCRL 1325, 1325 10000000, 0 0, 0, 0 ---------------------------------------------------------------- CRL split times: ---------------- Operation Time in ms ================================================ Copying delta CRL cache: 0 ------------------------------------------------ Preparing data for delta CRL generation: 0 Signing and encoding delta CRL: 8 Storing delta CRL: 96907 Delta CRL publishing: 177853 ------------------------------------------------ Preparing data for CRL generation: 0 Adding extensions: 0 Signing and encoding CRL: 14048 Storing CRL: 236265 Publishing CRL: 211122 ------------------------------------------------ Delta CRL total: 274768 CRL total: 461435 Total: 736203 ================================================
https://bugzilla.redhat.com/show_bug.cgi?id=675235
Metadata Update from @awnuk: - Issue set to the milestone: UNTRIAGED
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/1202
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
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)
Login to comment on this ticket.