Be the first to like this
We all want systems (cool websites, boring corporate applications) that respond quickly, and will not overheat our servers. In particular we want them to do that even if a lot of load is put on them. Getting that to work requires a lot of cooperation between developers and system administrators, to name but a few. Developers typically think that a performance problem can be solved with more hardware. After all, it runs great on their own laptop. How hard can it be? System admins typically think that developers are clueless about the real resource cost of load, or the laws of physics for that matter. It would help if these guys could talk to each other better. However, that requires a body of knowledge that is hardly taught well in schools. In my career I have seen quite a few systems that did not perform well under load, and actually got to figure out why. With these examples, this presentation will illustrate some of the important concepts in capacity and performance engineering. With these concepts we are working towards a ‘standard’ body of knowledge. With that body of knowledge dev and ops can work together to make systems that are more fun to use, simpler to manage and make more business sense.