Differences between current version and predecessor to the previous major change of Optimisation.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Saturday, September 18, 2004 8:48:23 pm | by StuartYeates | |
| Older page: | version 4 | Last edited on Wednesday, September 15, 2004 2:14:03 pm | by AristotlePagaltzis | Revert |
@@ -8,21 +8,20 @@
As a side effect, [Cache] locality of the code improves, so performance will often benefit as well.
This is the second most commonly referred to aspect of [Optimisation].
__Compilation time__::
Improves the perceived responsiveness of code compiled dynamically in reaction to user requests.
-__Threading
__::
+__Parallelisation
__::
Leverages the resources of [SMP] systems better, because MultiThreaded tasks can take advantage of multiple [CPU]s at once.
In practice, you always need a balance among these.
----
- Originally, StuartYeates
also listed
:
+There are other aspects which relate to the development-time rather than the run-time which can
also be thought of as optimisations
:
-
__Flexibility__::
-
Reduces the effort and thus cost of designing and implementing new features.
-
__Portability__::
-
Allows deploying the SourceCode on more than one platforms.
-
This often requires avoiding other, platform-specific [Optimisation] techniques.
+__Flexibility__::
+
Reduces the effort and thus cost of designing and implementing new features. See also [Refactoring]
.
+__Portability__::
+
Allows deploying the SourceCode on more than one platforms.
+
This often requires avoiding other, platform-specific [Optimisation] techniques.
- Personally
, I think it
is a stretch to file these as [Optimisation]s
. I have never heard them referred to as such, in any case. An appropriate term here is probably [Refactoring].
- <br>--AristotlePagaltzis
+Again
, balance
is necessary
.
