-
-
Notifications
You must be signed in to change notification settings - Fork 11.5k
Performance measurements #16791
Copy link
Copy link
Closed
Labels
branch: 3.0Applies to openssl-3.0 branch (EOL)Applies to openssl-3.0 branch (EOL)branch: 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 branchtriaged: 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
Activity
Metadata
Metadata
Assignees
Labels
branch: 3.0Applies to openssl-3.0 branch (EOL)Applies to openssl-3.0 branch (EOL)branch: 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 branchtriaged: 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
- StatusShow more project fieldsDone
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_tolowerandossl_ctype_checkuse 6-7%.