The WorkRandomnessUpdateMonitor used to use used to get random books from the materialized view, but we use ES for that instead now. So this UpdateMonitor can potentially be removed. 

In my instance this monitor is causing a large DB I/O spike every night, since it is run against all works, and this happens every for every collection in the CM so it does [works * collections] updates. This could be mitigated by changing the monitor, but since the monitor can be removed anyway it doesn't have to be.