[virtuald]

FWIW, in the past NetworkTables has had locking issues. However, it was completely rewritten this year by someone I trust to write it correctly, but it's possible that there are some issues somewhere that haven't been caught yet.

Even without bad locking issues causing delays, I'd be willing to bet that each read of a NetworkTables variable is going through a lock (I haven't looked at this year's code) or two, so it will add up a little bit... though, probably not 75ms worth (take it out, see what happens?).

The way I get around this latency in pynetworktables is we provide "auto update values" and ntproperty, which just create a placeholder object that you can read from atomically without taking a lock. The object gets updated by a subscriber which will update the value anytime an update is received from the network -- so it's only changing when the value actually changes.