Hi Raneen, Thank you for reaching out to us. I see that you have a question about concurrency requests. While we don't limit the number of concurrent threads a client application can have, concurrently sending requests via an unlimited number of threads can easily exceed the Requests Per Second limit at the developer token level. We recommend that you set a reasonable upper bound for the total number of concurrent threads that are going to make requests (across all processes and machines), and adjust upward from there to optimize your throughput without exceeding the rate limit. Furthermore, you can consider throttling QPS from the client side across all threads, and read more about these best practices here. Let me know if you have further questions.
Thank you, Bryan, Google Ads API Team ref:_00D1U1174p._5001UZZ0Qv:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/kbQJm000000000000000000000000000000000000000000000Q93GKY00_jBieubbSqmlp9xQrgmnZg%40sfdc.net.
