Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You should always have a good idea of what part of the codebase will be the bottleneck when you write it. If you have that just optimize the things it spends time on. The only time you really need a profiler before optimizing is when you are micro optimizing to try to handle cpu ordering etc, other than that performance is mostly predictable.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: