serpapi
[Google Trends API] Performance degradation
One of our high-volume customers reported that they are getting elevated response times. Looking at the performance, it appears that it started degrading after a short period of being more stable.
Not sure if connected with any of the other Google Trends issues.
Internal links: Intercom
Seeing a large dip in success rates on the Google Trends API, in addition to an increase in response time.
Not sure if this is related to #2063, or if we should keep this issue open as well.
Additional reports:
@tanys123 A customer reported a Google Trends query that took 264 seconds and succeeded. Have we changed anything with our timeout limit? I would've expected that to fail at 90 seconds.
@tanys123 A customer reported a Google Trends query that took 264 seconds and succeeded. Have we changed anything with our timeout limit? I would've expected that to fail at 90 seconds.
Was the customer enable search with async? We do have longer time out for async searches.
@tanys123 A customer reported a Google Trends query that took 264 seconds and succeeded. Have we changed anything with our timeout limit? I would've expected that to fail at 90 seconds.
Was the customer enable search with
async? We do have longer time out for async searches.
Thanks @tanys123 They didn't mention anything about async, but it was in the API Playground. Do we have a longer timeout for Playground?
Yes, playground is using the async endpoint to fetch that in-progress status.
Yes, playground is using the async endpoint to fetch that in-progress status.
Got it. Thanks for clarifying @hartator.
We have seen better performance for the past month compare to when this issue was first reported. It is also more stabilized for the past week. I am closing this but we will keep monitoring the API.