Improve Move Calculator Performance

[lordscarlet]

The "Move calculator" gives a warning that it may take approximately 30 seconds. I just tried to run it on https://www.choochoo.games/app/games/716, and I started typing this up after it hit the 13-minute mark.

I have an algorithm that, in theory, improves things (in all honesty, Copilot wrote it, not me), but I don't have good data to test it on. @YourDeveloperFrien,d is there an easy way for me to seed my data for a good test?

[lordscarlet]

FWIW, I tabbed back after this and it was done. So somewhere between 13 and 16 minutes.

[lordscarlet]

I was able to use the API for my production game to dump it into some metrics.

I'm not 100% sure on my metrics, as they say it took 35 minutes with the original, which is not what I saw in the real world.

Having said that, I have gotten those 35 minutes down to 47 seconds, which is a 98% decrease.

I don't know that there are any tests around the move calculator, but all tests are still passing locally.

[YourDeveloperFriend]

It took you 13-16 minutes? I've never seen it take longer than 2 minutes, but I admit it can be slow. Can you create a PR? I can pull in the changes and verify the difference.

[lordscarlet]

It's possible there was something very particular in the routes in that game.

I need to clean up the code a lot and then I will make a PR.

[Sleipmaersk]

I think performance could be better if you could set Loco from - to.
I only use it when I have loco 5 or 6. I don't need 25 suggestions for loco 1, 2 and 3 ... :)