In my test setup, the tool was not moving at all, so I just run a similar loop about 500 times. The first run is about 0.5 second while the last one was 2 seconds. The only thing change is that new values are updated to fields at the end of each increment. My guess is that querying data from fields is getting slower when the field contains more time increments. At first, the field is interpolated in time direction here, and I don't immediately see any reasons why fetching the newest value from the field should slow down as the size of the data vector grows.
In my test setup, the tool was not moving at all, so I just run a similar loop about 500 times. The first run is about 0.5 second while the last one was 2 seconds. The only thing change is that new values are updated to fields at the end of each increment. My guess is that querying data from fields is getting slower when the field contains more time increments. At first, the field is interpolated in time direction here, and I don't immediately see any reasons why fetching the newest value from the field should slow down as the size of the data vector grows.