Hunting down performance issues. A small DevOps story.

Here comes the story of another operation:

One of my services (I both develop and operate it) frequently does "checks" on proxies through another service. This means a lot of service calls and some cryptography happening in the background so I was expecting it to use the CPU. The odd thing I was not expecting is that it did many many checks. For context, The check cycles were taking hours.

This had me puzzled for some time and …

cpu cryptography devops down hunting lot metrics performance problem proxies service services story web