Findroute: initial loading and filtering efficiency

[jteresco]

The Route Finder is obviously very slow to load, since it brings in information from all 60,000+ routes from the DB, transfers it using JSON, processes it in JS, and then the browser needs to display the results of DOM changes.

Places to look for efficiency opportunities:

• more efficient SQL query (reduce DB access time)
• smaller data resulting from SQL query (reduce encoding/transmission/decoding time)
• thinking about how the table is built in JS to be more efficient on construction and when filters are applied (reduce time spent by the browser)

[jteresco]

Recent configuration changes to the DB server have sped up large queries like the one findroute uses. A page load on my Mac now takes roughly 7 or 8 seconds for the DB query and another 7 or 8 seconds to apply filters initially.