Profilers – when and where?

Please be sure to check out the team blog we have here

This has the most input from the broader team on profiling and performance issues.  I'll talk somewhat in my blog about some of the technology we use, but that site is always your best bet.

For the moment, I'd like to solicit feedback about when and where people are using profilers to figure out performance problems.  Is it mostly in the field, after apps have been deployed, or before deployment on the devs desktop?  What issues do you encounter when you try to profile in those scenarios with existing tools?


Comments (4)

  1. Jason Ronald says:

    In our case it is most important once it has been deployed. We can analyze the application as much as we want in the development cycle, but there is always a customer’s environment that exhibits performance problems that we can never recreate in our test lab. In those cases, it would be great to have the ability to profile the specific environment having problems.

  2. JoC says:

    Thanks Jason. With what success have you used performance analysis tools in the deployed case like this. Are there particular hurdles you have had to jump over? What types of deployed apps are we talking about here

Skip to main content