Detecting and preventing performance regressions in code.

Change is a part of life. After you are done with your code it will evolve in time. Those modifications are not always performed by you (the author) that knows that code inside out. Sometimes there are done in a hurry or without detailed specification. Because of that, in time, that code may become less efficient. It might need more time, more CPU or more memory. In this talk, I will walk you through and demonstrate an open-source tool that I’m working on from some time – a greatly enhanced fork of a well-known tool. It will show you when your code starts to deteriorate and It will help you to keep it in great shape.