JENKINS-23244. It is a little complicated since the node build history page shows both a textual table, which is rendered incrementally; and a graphical timeline, which is not rendered incrementally (blocks a handler thread getting data), and which only shows 20 records (if it ever gets that many!) as a partial workaround.
Even if everything is rendered incrementally (and, in the case of the timeline, also on demand by scrolling), leaving the page open (or scrolling) could impose a burden on the server, though at least there is no risk that some runaway thread will freeze the server indefinitely: you just need to navigate away. Maybe UIs like this could impose some kind of throttling, so that only up to 10 build records per seconds could be loaded in the entire system in response to UI navigation (batch processes could be exempted).