Hi Daniel, thanks for trying out the tool. We will handle the issues that are created on GitHub, and we can keep the discussion going there so we have a single point of contact, but because this wasn't clear before, I am answering your post here so you can keep track.
First thing to remember, is that the tool still under development and we choose to open it to the community so we could collect this kind of feedback, and improve with new features and better performance based on user's needs. The current version on GitHub might solve your problem with very big accounts. It was added a property to control the rate that rows are parsed and persisted into the DB. Could you test the new version of the tool with your account, please? If you have other feature requests (like saving the CSV files) or suggestions for improvement, please create it on GitHub so we can keep track of everything. Also remember that if you know how to solve a problem, and are willing to do so, you can always do a pull request to the repository, and help everyone that is using the tool. Thanks for your time, and let us know if you have any other problem. Cheers. Em quinta-feira, 21 de novembro de 2013 12h30min14s UTC-2, Daniel Altman escreveu: > > Hello, just wanted to point out how disappointing we are with AwReporting > and why. > > We were told AwReporting would be the solution to our problems regarding > downloading large scale performance information for all our accounts. > We currently do nightly downloads using the API, calling it in parallel > and inserting the reports directly into external Hive tables. > > We were facing a lot problems like ERROR_GETTING_RESPONSE_FROM_BACKEND due > to the fact that we have accounts with for example 7 million ads. > Of course we retry, but sometimes, we get the error 10 times or more and > the API es very slow also when downloading those accounts. It seems times > grow exponentially compared to account with half the size. > > > We were expecting AwReporting to solve that, but: > > 1) It uses the same API, so basically it is the same code we have already > written => same problems with large accounts > 2) It does not allow us to save directly to CSV, or TSV files that could > be directly used in Hive tables, as many of the one managing large datasets > are probably doing. We cannot save the data to a DB just to transform it > later. > 3) It creates all the objects in memory and uses Hibernate to save the > objects into the DB?!?! We are getting "Out of memory" exceptions for > almost all our accounts. > > > Simply put, I don´t think this will work for any large-scale API consumer. > Either you don´t care, or you didn´t make the proper effort into > understanding our real needs. > > In any case, is very disappointing. > Let me know if we can help in any way to make this a real useful solution. > > > Daniel Altman > Despegar.com > > > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://googleadsdeveloper.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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. For more options, visit https://groups.google.com/groups/opt_out.
