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

Poor performance of API requests #187

Open
kynan opened this issue Oct 15, 2015 · 4 comments
Open

Poor performance of API requests #187

kynan opened this issue Oct 15, 2015 · 4 comments
Assignees

Comments

@kynan
Copy link
Member

kynan commented Oct 15, 2015

Since the upgrade to MongoDB 3.0 and Eve 0.6 (taarifa/TaarifaAPI#9) it seems API requests perform even more poorly. Heroku imposes a 30 second timeout on requests and we're already scratching that for a mere 100 waterpoints.

@kynan kynan self-assigned this Oct 15, 2015
@kynan
Copy link
Member Author

kynan commented Oct 15, 2015

Funny enough the waterpoints requests seem to be properly cached on subsequent page loads, however region_name and district_name apparently not.

@kynan
Copy link
Member Author

kynan commented Oct 15, 2015

I haven't figured out why Angular refuses to cache these client side, but I have added server side caching, which is probably the better approach anyway, given that this data rarely changes.

@kynan
Copy link
Member Author

kynan commented Oct 16, 2015

This issue is a total killer for the dashboard: we don't even get close to serving any API requests within the 30s timeout (certainly not for the national dashboard).

@kynan
Copy link
Member Author

kynan commented Oct 29, 2015

Partly mitigated by caching responses from the /api/waterpoints/values endpoints (986d682).

kynan added a commit that referenced this issue Dec 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant