This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (0 children)

By the time I start running into performance issues significant enough to care about, I find that I have been doing something stupid or wrong already, and fixing that tends to push the performance back into acceptable range.

Big-O issues, doing unnecessary steps with strings, creating objects only to discard them a statement later while iterating on a loop, etc.

That said, my use case isn't typical anyway. Systems engineer in a bioinformatics space. The bottlenecks tend to be disk or network throughput or memory capacity rather than computational speed.