 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
| • |
So,
evaluate your performance needs and...
|
|
|
|
– |
consider
how much memory one approach requires
|
|
|
|
over
another
|
|
|
|
– |
evaluate
the strengths/weaknesses of the algorithms
|
|
|
|
themselves
(are there certain cases that are not
|
|
|
|
handled
effectively?).
|
|
|
|
– |
Overall,
it is important to examine algorithms for
|
|
|
|
both
style and efficiency. If your problem size is
|
|
|
|
small,
don't over analyze; pick the algorithm easiest
|
|
|
to
code and understand. Sometimes less efficient
|
|
|
|
algorithms
are more appropriate.
|
|