Improve performance (pagination and search) of TP's tables

[mitchell852]

I'm submitting a ...

• bug report
• new feature / enhancement request
• improvement request (usability, performance, tech debt, etc.)
• other

This would be an improvement for TP and a potential enhancement to the TO API.

Traffic Control components affected ...

• CDN in a Box
• Documentation
• Grove
• Traffic Control Client
• Traffic Monitor
• Traffic Ops
• Traffic Ops ORT
• Traffic Portal
• Traffic Router
• Traffic Stats
• Traffic Vault
• unknown

Current behavior:

Currently TP fetches ALL records (i.e. servers, delivery services, etc) from the TO API and does the pagination and search on the client-side in the browser. As the number of records grow, the amount of time required by jquery datatables to render the TP tables and the amount of browser memory required to do this grows. Eventually that memory may run out and TP tables may become unusable.

Expected / new behavior:

2 possible solutions:

1. Implement a better table library
2. push the pagination and search to the server-side (the API) and leveraging some of the existing as well as some new features of the API.

Minimal reproduction of the problem with instructions:

Create thousands of records (i.e. servers) and navigate to https://tp.domain.net/#!/servers and watch how long it takes for the table to render.

[mitchell852]

this is only actually fixed for the servers table of TP. not all of the other tables. reopening.

[mitchell852]

going to close this as a new ag-grid was introduced to deal with problematic tables.