Skip to content

Golang Profiling: Brief Guide #104

@matthawkins90

Description

@matthawkins90

I'm trying to teach myself Go.
In order to get a good idea about possible low-hanging-fruit that could be optimized in our software, I think it would be good to briefly document how to profile golang code.

I think it would fit nicely in the Contributing section of the docs.

I'm going to work on this, but I would welcome any tips from devs who are experienced at profiling in golang, and who have any suggestions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions