...
Solving the traveling salesman problem is expensive. Doing it server-side is too expensive (it would cost us more than our total server cost at the moment).
So we have opted for the second best solution. We use the same code as used in the GSAK macro that does the same, and our TSP tool use Google Maps and client-side processing. It is memory intensive, and will take some time for longer routes.
We recommend that you only use this tool for trips with less than 80 waypoints, or at least with only 80 waypoints at a timeWhich is one of the reasons why we don't do it automatically.
You are only able to use this with up to 80 waypoints, but you can optimize several times, and in that way make it work on a larger trip.