Okay there are now quite a few posts pointing out that you can use a speed controller linked to one off actuator block and also linked to all the single block docking rails to turn off movement checks and reduce lag. This works cause the rail even if just one block is still checks to see if the docked entity can move and checks for collisions. By setting the rail to 0 speed it reduces the calculations the server/computer needs to do.
Extending this idea to rails that have to move. You could put an actuator at the end of the rails which through a NOT block would turn off the actuator linked to the speed controller. So at the end of the movement the rail speed is set to zero. Then setup the rail movement logic to turn on the actuator linked to the speed controller when you do want to move it. This way that railed entity will only generate a bit of lag while actually moving.
Obviously this won't work on a rail entity that is constantly moving.
Extending this idea to rails that have to move. You could put an actuator at the end of the rails which through a NOT block would turn off the actuator linked to the speed controller. So at the end of the movement the rail speed is set to zero. Then setup the rail movement logic to turn on the actuator linked to the speed controller when you do want to move it. This way that railed entity will only generate a bit of lag while actually moving.
Obviously this won't work on a rail entity that is constantly moving.