It's a bit like a closed loop: 1) Reporting API does not support sorters and paging, so you end up getting data you don't really need which increases response time. 2) All the requests are super slow anyway, so you have to implement caching with multi-threading. The slower it gets, the more threads you use. Multiple companies hammering reporting API this way, obviously doesn't improve API performance. 3) Finally from time-to-time the API stops responding in timely fashion at all or starts throwing 500 errors (happens relatively often these days) and *the engineers* apply some temporary work-around which doesn't solve the real issue and we are back at point 1.
-- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/042afa7c-a4f5-494a-9355-8e882f9f1057%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
