feat(wirey): adds cpu profiling

[RohanSreerama5]

This is part of an effort to do some CPU profiling of the Wirey binary. This will bring visibility into Wirey's "hot" functions and how we can go about optimizing the code better. (hot refers to the most frequently invoked functions.)

First deploy this binary into production. Then, we can see the following:

CPU profile: curl http://localhost:6060/debug/pprof/profile?seconds=30 (Collects 30 seconds of CPU profiling data)
Heap profile: curl http://localhost:6060/debug/pprof/heap
Goroutine profile: curl http://localhost:6060/debug/pprof/goroutine

It can also create a Flame graph to indicate the most frequently used functions across the call stack.

What is paramount here is that the CPU profiling is done on a production load, so that the optimizations derived from this effort impact usage behavior of actual users of Wirey.

BTW:
With Profile Guided Optimization (PGO), Golang will also perform optimizations on such "hot" functions and give you back data about the performance increase it might've yielded. Optimizations refer to compiler passes such as inlining, constant folding, etc etc

We can run profiling as optional setting like so:
./myapp -enable-profiling=true -profile-addr="localhost:6061"

[marcotuna]

Hi @RohanSreerama5,

Thanks for adding the profiling feature! I have a couple of suggestions:

• Make Profiling Optional: Since profiling can introduce some overhead to the application, and the current implementation opens a port by default, it would be better if we could enable it through a configuration setting or command-line flag. This way, we only turn it on when we really need it.

• Listen Address: It would be helpful if the host and port for profiling could be set in a config file or as a command-line option. This gives us more flexibility and avoids possible conflicts with other services.

What do you think?

[RohanSreerama5]

Hi @RohanSreerama5,

Thanks for adding the profiling feature! I have a couple of suggestions:

• Make Profiling Optional: Since profiling can introduce some overhead to the application, and the current implementation opens a port by default, it would be better if we could enable it through a configuration setting or command-line flag. This way, we only turn it on when we really need it.
• Listen Address: It would be helpful if the host and port for profiling could be set in a config file or as a command-line option. This gives us more flexibility and avoids possible conflicts with other services.

What do you think?

Totally agree, that's a great idea. I've pushed up a commit to address this. Should be able to invoke it like so:
./myapp -enable-profiling=true -profile-addr="localhost:6061".