Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m just curious really, there doesn’t seem to be any counter arguments. So should a profiler be used for everything? I’d imagine the performance gain would require make it beneficial every time.
If you have a very performance-critical application, then profile as much as possible during your development cycle so you can find your potential bottlenecks as early as possible and adjust your designs around them.
Otherwise, only profile when you run into an unexpected performance problem, have questions about the performance of specific algorithms or subsystems, or near the end of the development cycle if you have time leftover to work on improving performance even if it’s not strictly necessary.
In most cases getting the application to work as expected on time is much more important than getting it to run fast, and profiling can eat up a lot of development time.