Anash,

Thank you, I will try this.

Also, most documentation says use up to 10 threads, but the Java 
example<http://code.google.com/p/google-api-adwords-java/source/browse/apps/multipleclientreportdownloader/src/com/google/api/adwords/reportdownload/MultipleClientReportDownloaderMain.java>uses
 20.  Is 10 concurrent requests still the recommended number?

Thanks,
-Adam

On Tuesday, March 27, 2012 2:43:31 AM UTC-4, Anash P. Oommen wrote:
>
> Hi Adam,
>
> You can switch the clientCustomerId at runtime by doing
>
> (user.Config as AdWordsAppConfig).clientCustomerId = newvalue;
>
>
> Cheers,
> Anash P. Oommen,
> AdWords API Advisor.
>
> On Friday, 23 March 2012 18:34:20 UTC+5:30, Adam Weiss wrote:
>>
>> We successfully switched from MCC reports to multiple AdHoc reports, but 
>> are finding that it is taking significantly more time to finish than it did 
>> in v13.
>> We are doing up to 10 concurrent threads downloading reports via the 
>> ReportUtilities in the .NET client library.
>>
>> Each thread is doing the following:
>>
>> try
>> {
>> var user = new AdWordsUser(new Dictionary<string, string>() { 
>> {"clientCustomerId", account} });
>> var reportUtil = new ReportUtilities(user);
>> var filePath = clientPath;
>> reportUtil.DownloadClientReport(reportDef, filePath);
>> }
>> catch (Exception e)
>> {
>> ...
>> }
>>
>> Is there any way to avoid having to create a new AdWordsUser each time? 
>>  Or is there a more efficient way to do this?
>>
>> Thanks,
>> -Adam
>>
>

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.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

Reply via email to