Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too slow when data set is large #146

Open
alexsoble opened this issue Feb 23, 2015 · 7 comments
Open

Too slow when data set is large #146

alexsoble opened this issue Feb 23, 2015 · 7 comments

Comments

@alexsoble
Copy link

When larger datasets come into play, the loading/filtering is too slow for the app to be practical. Child care finder: http://codeforboston.github.io/child-care-finder/. Testing from home, takes around 20 seconds of loading before I can interact and another ~20 seconds when I click on a filter or map. Maybe caching could help here? Or loading less data? The map initializes with a view of the Boston area, but I have a feeling it's pulling in every location in MA before the user can interact with the map.

child-care-finder

@radumas
Copy link

radumas commented Feb 26, 2015

Do you now how many datapoints are in that set? I'm having a hard time testing finda with my own dataset (originally 924, now down to 100) and seeing whether the interminable loading is a bug I've introduced or the dataset.

@alexsoble
Copy link
Author

Based on GitHub's data.geojson visualization, it looks like there are 8,260 points in the child care finder set.

@djq
Copy link

djq commented Mar 4, 2015

Would something like http://turfjs.org/ help? You'd still need to load the data (somewhere) but it could be filtered to the map bounding-box, which would speed up rendering

@paulswartz
Copy link
Contributor

There is some filtering already; if you let the data load you can see a "limit to map" check box in the filters. The way it works is by loading the data, and then using the map bounds to limit what is displayed by the map/list.

I recently did some work around making the performance better, but I'd love for someone else to look into it too!

@radumas
Copy link

radumas commented Mar 12, 2015

A thought: Could it be the enabling text-searching that builds an index when the site first loads that takes a lot of time for larger datasets?

@paulswartz
Copy link
Contributor

There's also the index we build for the filter on the sidebar, and adding
that many points to the map in the first place.

On Thu, Mar 12, 2015 at 2:09 PM radumas notifications@github.com wrote:

A thought: Could it be the enabling text-searching that builds an index
when the site first loads that takes a lot of time for larger datasets?


Reply to this email directly or view it on GitHub
#146 (comment).

@alexsoble
Copy link
Author

@paulswartz @radumas -- Will you be at CfB this Tuesday? I'll be there, let's pair on this together if we can both make it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants