misaugstad
commented
3 years ago Yeah I was just testing around, and found that I was consistently getting a load time of 7 seconds for Seattle, 2.5 seconds for SPGG, and 1 second or less everywhere else. Seattle and SPGG are definitely the cities with the most data, but I have no idea which queries are taking a long time when preparing the landing page. Just doing the straight up count of the labels or validations should be instantaneous (verified by running those queries directly on the database). And checking the audited distance is something that we are caching (and I was getting the full 7 second load time on consecutive page loads, so the cached value should be there).
Looks like we need to do some profiling! I just asked Jason for database permissions for the new tables that we added. Once I've got those, I will create a database dump of Seattle so that we have the full thing to test with.
It looks like the /neighborhoods endpoint could be made more efficient. The set of queries to get the list of neighborhoods looks pretty wacky and should be simplified. Might speed things up a bit. Take 1-1.5 seconds in Seattle, ~0.1 seconds everywhere else. But I think that that actually doesn't prevent the page from loading; I think that the map showing up is just delayed for an extra second.
jonfroehlich
Brief description of issue/feature
When loading the webpage at https://sidewalk-sea.cs.washington.edu/, it takes a long time to load for the first time. Have noticed this on Chrome and Firefox. @uditpatwal and @misaugstad have also noticed the slow load times. The server may be overloaded?
Expected behavior
Faster load times (hopefully below a second!)
Current behavior
takes from 3-5 seconds to load (which feels way slower as a user)
Steps to reproduce
go to https://sidewalk-sea.cs.washington.edu/