Rudder

In #5452, we optimised the time taken to display the list of nodes page.

We can go much more farther on that with one of the two following architecture modification:

1/ only load node info actually displayed. This - of course - allows to transfer a lot less datas, but it need to rething how nodes paging/filtering/sorting is done: today, it's all JS-side (quick and "work as expected"), here, it will need ajax request for each click (with new data transfert each time)
2/ keep a live client-side data structure about nodes, and use it everywhere. The idea is that nodes info are not changing often (beside the "last view"), so we could have a comet client-side view of the datas, updated only with diff (and so, with very few modification each time). This need some modification in the backend.