.NET has several options to deal with this problem.
First, there is multithreading. Just run multiple threads at the same time, each thread doing (say) 20 reports. Another possibility is asynchronous processing. Pro-tip: if you go this way, add the following to app-config:
<configuration>
<system.net>
<connectionManagement>
<add address ="*" maxconnection ="1000"/>
</connectionManagement>
</system.net>
</configuration>
Item "maxconnection" is the key member. Look it up.
Note this all depends on your definition of slow, and the times you wish to achieve. To give you a baseline, my C# code processes 280 accounts in 2.5 hours, with about 30 reports for most accounts - and these reports are all much bigger than an ACCOUNT_PERFORMANCE_REPORT. Processing means requesting reports, downloading and decompressing them, uploading to SQL Server, and processing them in SQL Server.
I suggest you add start extensive logging to figure out what exactly takes such a long time. For instance, in my situation 75% of the time goes to SQL processing.
On Thursday, June 23, 2016 at 4:06:43 AM UTC+2, Abdurrahman Al Faruqi wrote:
-- First, there is multithreading. Just run multiple threads at the same time, each thread doing (say) 20 reports. Another possibility is asynchronous processing. Pro-tip: if you go this way, add the following to app-config:
<configuration>
<system.net>
<connectionManagement>
<add address ="*" maxconnection ="1000"/>
</connectionManagement>
</system.net>
</configuration>
Item "maxconnection" is the key member. Look it up.
Note this all depends on your definition of slow, and the times you wish to achieve. To give you a baseline, my C# code processes 280 accounts in 2.5 hours, with about 30 reports for most accounts - and these reports are all much bigger than an ACCOUNT_PERFORMANCE_REPORT. Processing means requesting reports, downloading and decompressing them, uploading to SQL Server, and processing them in SQL Server.
I suggest you add start extensive logging to figure out what exactly takes such a long time. For instance, in my situation 75% of the time goes to SQL processing.
On Thursday, June 23, 2016 at 4:06:43 AM UTC+2, Abdurrahman Al Faruqi wrote:
Hi guys, I know we cannot get all account performance report using MCC.I am able to get the data but it takes so long because I have to call API's multiple times, in my cases it took 120 calls because of in my case i have 199 accounts.what Im doing is using ManagedCustomerService and then call one by one of the accounts using awql ACCOUNT_PERFORMANCE_REPORT . And it takes so long.my question is any better idea to workaround with this problem?Some people using ReportUtilities.GetClientReport() method here, how do this works? I can't find enough documentation or examples about this method. by the way I code with C#.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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+unsubscribe@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+unsubscribe@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/0a49b992-064e-4d93-b2de-a1bd44dfe7c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment