You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,8 @@ Before trying to optimize, one has to measure and identify what needs to be opti
47
47
48
48
That being said, one should always try to optimize and produce efficient solutions. A non-efficient "solution" can be as good as no solution at all, if not worse.
49
49
50
+
**Pre-optimisation is perfectly valid given pre-knowledge**. For example that instantiating a whole class or array is slower than just returning an integer with the appropriate information.
51
+
50
52
Some of the optimization techniques can be automated (eg in compilers), while others are better handled manually.
51
53
52
54
Some times there is a trade-off between space/time resources. Increasing speed might result in increasing space/memory requirements (__caching__ is a classic example of that).
0 commit comments