-
Notifications
You must be signed in to change notification settings - Fork 7
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
Full-text search is slow #1573
Comments
Saw some more worker timeouts today, and here are the surrounding log entries: Looking at these logs, it is hard to immediately discern a pattern to the requests, they almost seem random (e.g. page 65 for a nonexistent target) . Some of these might be slower than others but the thing that strikes between all three of these times is that it's a lot of requests at once. But also it doesn't really seem like so far out of line with what we're getting, say, in the middle of the day? |
Do you think it's a deliberate DDoS? Someone trying to inflate the usage metrics on our filters 😉? |
As of right now, the code from #1626 is deployed on staging, making direct comparisons with production somewhat straightforward. With https://staging.pressfreedomtracker.us/all-incidents/?search=arrested, I'm getting ~3-3.5 second times. With the same query in production, https://pressfreedomtracker.us/all-incidents/?search=arrested, I'm getting ~6 second times. |
🔥 |
As follow-up from our discussion around creating a clear performance goal, I started this new "Scalability & Performance" page in the wiki as a starting point: https://github.com/freedomofpress/fpf-www-projects/wiki |
We observed a number of timeouts over this past weekend. Trawling through the logs, Cameron noticed around those timeouts some slow requests for pages that included a text search term. I am able to reproduce that performing a text search on the tracker website takes several seconds to respond: https://pressfreedomtracker.us/all-incidents/?search=antifa
Let's find ways to improve performance here. I'll set the bar for closing this ticket as consistently achieving <1s responses for filtering queries involving text searches on the database page.
Some ideas that came up in discussion:
The text was updated successfully, but these errors were encountered: