Monday, November 11, 2013

Understanding Windows Task Manager readings

Windows Task Tanager is a well known and frequently used software in windows. At least by the programmers. Developers mainly use Task Manager to close their ever running, not responding or slow programs. But actually what those reading tells us? 

It tells us about the Applications which are running, the Processes details, Windows Services information, network usage,Users who are all logged into the system along with overall system performance.

Recently I was interviewing so many developers for filling a position in "Performance & Memory team". Initially we were looking for people who have experience in performance profiling and memory optimizations. But no luck. Then we thought that we can give training to the people but he needs to be well aware of .Net internals. Again there was no luck. Finally we are trying for somebody who knows how the computer is functioning. I think if the developer, who don't know how his program is executed by the operating system, is not a good fit for performance team where he need to analyse other's code and improve its performance. One question I used to ask the candidates is about Task manager. Most of them, says "Sorry, to get my program working, I don't need to know about the readings in Task manager and it's interpretations and I survived 5-7 years in the field". I believe that by domination of managed execution environments such as Java & .Net, people forget about the machine which is actually doing their tasks. Sometimes I felt that understanding the system reading was not there in any of the programming books. 

This is just a simple initiative to aggregate the tutorials which will explain how to interpret the Task manager readings to a developer.

No comments: