Nearest read preference should take account of database load
I understand it only take account of network latency however this node can have high load and would give a poor response. Instead, I wished the driver would contact the more distant network latency node that has less CPU/memory load.
1
vote
![](https://secure.gravatar.com/avatar/3acf83ad34ce7ad329c517e8a9719183?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)