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

Decrease url granularity for polling for new incidents #26

Open
evoltech opened this issue Apr 25, 2012 · 0 comments
Open

Decrease url granularity for polling for new incidents #26

evoltech opened this issue Apr 25, 2012 · 0 comments

Comments

@evoltech
Copy link
Member

The url generated tor polling for new reports from the Ushahidi API is now per second. If we get a lot of clients polling, even if there is a short poll frequency it will be hard to cache the response in the forward proxy.

This issue may be handled by some intelligent configuration of the forward proxy (ie all requests for /api/?task=decayimage&by=sincedate&date= and the proxy never makes back-end requests, but only allows invalidations from the Ushahidi master). Without limiting the API cache to only serving explicitly invalidated caches we could also make sure that has a max resolution of a minute instead of second. This would change the worst case scenario from n back-end requests per second to 1 back-end request per minute to cache API requests.

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

1 participant