-
-
Notifications
You must be signed in to change notification settings - Fork 11.1k
Closed
Labels
branch: 3.0Applies to openssl-3.0 branchApplies to openssl-3.0 branchbranch: 3.1Applies to openssl-3.1 (EOL)Applies to openssl-3.1 (EOL)branch: 3.2Applies to openssl-3.2 (EOL)Applies to openssl-3.2 (EOL)branch: masterApplies to master branchApplies to master branchinactiveThis label should not be applied to open issues anymore.This label should not be applied to open issues anymore.triaged: bugThe issue/pr is/fixes a bugThe issue/pr is/fixes a bugtriaged: featureThe issue/pr requests/adds a featureThe issue/pr requests/adds a featuretriaged: performanceThe issue/pr reports/fixes a performance concernThe issue/pr reports/fixes a performance concern
Description
I tried to profile the example from #16540
We spend ~20% of time in various lock/unlock functions.
Also we spend ~20% of time in ossl_parse_property. It may partially overlap with lock/unlock but looks like a hotspot to me.
Also various ossl_tolower and ossl_ctype_check use 6-7%.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
branch: 3.0Applies to openssl-3.0 branchApplies to openssl-3.0 branchbranch: 3.1Applies to openssl-3.1 (EOL)Applies to openssl-3.1 (EOL)branch: 3.2Applies to openssl-3.2 (EOL)Applies to openssl-3.2 (EOL)branch: masterApplies to master branchApplies to master branchinactiveThis label should not be applied to open issues anymore.This label should not be applied to open issues anymore.triaged: bugThe issue/pr is/fixes a bugThe issue/pr is/fixes a bugtriaged: featureThe issue/pr requests/adds a featureThe issue/pr requests/adds a featuretriaged: performanceThe issue/pr reports/fixes a performance concernThe issue/pr reports/fixes a performance concern
Type
Projects
Status
Done