Why should you profile? Watch the webinar to find out the right tools for the right job when profiling on both the server and client side. We’ll show you how to profile your application code and see what features compare from one profiler to the next.
Below is a preview of the webinar transcript.
Why should we bother profiling? What reasons are there for us to even spend time looking at code running in our environments? Well, if we’re making assumptions about what’s going on, what’s running in our environments then we’re really treading on dangerous ground. We need to be working with facts. We need to understand why we’re having problems if we’re having problems and if we don’t use profilers then we can never really get to the root cause of what the problem is.
There was a study done in 2005 at Carnegie Mellon where they were looking at causes of failure in web applications. 80% of unplanned outages are due to ill-planned changes made by operations or developers is what they found. They also found that 60% of availability and performance errors are the results of misconfigurations. Looking ahead through 2015, 80% of the outages impacting mission critical services will be caused by people and process issues. More than 50% will be caused by change, configuration, release integration and hand-off issues
Finally, 80% of all the incidences are caused by changes made to the IT environment including application code. Not just configuration problems, not just configuration changes but even hand-off issues, deployment problems, issues with the application code itself. If we’re not using profilers, many times we don’t really have a good feel, we don’t have the facts to know the root cause for why we are dealing with the issues and facing the problems that we’re facing.
Fill out the form to the right to watch the webinar in its entirety. >>