Skip to content

Performance measurements #16791

@beldmit

Description

@beldmit

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%.

Metadata

Metadata

Assignees

No one assigned

    Labels

    branch: 3.0Applies to openssl-3.0 branchbranch: 3.1Applies to openssl-3.1 (EOL)branch: 3.2Applies to openssl-3.2 (EOL)branch: masterApplies to master branchinactiveThis label should not be applied to open issues anymore.triaged: bugThe issue/pr is/fixes a bugtriaged: featureThe issue/pr requests/adds a featuretriaged: performanceThe issue/pr reports/fixes a performance concern

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions