where in this case it would not be fast enough or the wrong method..

What I stated was, that if the code is fast enough for the purpose it
is used in, there are other things to work on, than
wasting time on optimization.

--

I have a pathfinding for RTS units on a mobile phone game (Java phone)
that can find a path in realtiime for hundreds of objects with no
remarkable slowdown.
It is then just using a more appropriate metod than
a classic A* pathfinding.
Where it would not be as fast for single units.

The initial choice of the method is more important than the optimization of it.