-
Notifications
You must be signed in to change notification settings - Fork 11
Open
Description
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
Labels
No labels