When you xport it has to calculate the distance to each ship in the list, even if the list is aborted. Makes sense of course, since the game as to deny the xport if it's out of range. But the time required increases with every ship on the list, so it appears as if it's doing a separate distance search for each ship. But perhaps the same BFS queue could be used for all of the ships, which would dramatically reduce the amount of CPU use.

This is a problem in games where a lot of ships are in use and people xport a lot. It can cause some serious CPU spikes.

Maybe changeing the defualt CPU priority to Normal rather than High in the
server configure tab may make for more balanced cpu activity.

It's already set to normal. The CPU load problem had to do with TW recalculating the warp course for every ship in the xport list, even if you abort the display. That means running a course search dozens, maybe hundreds of times, without any text flow to pace things.

I believe this was solved in an earlier beta. I believe JP made the list truly abortable, so that it doesn't need to calculate the distances if you abort the list anymore.