Re: Concurrent requests not working on our production server

2013-04-03 Thread Stephane Guerin
Ho... looks like the trouble might be related to the fact that we use 
Windows 2008 Web edititon. Dang.

Stéphane

On Wednesday, 3 April 2013 14:09:49 UTC-4, Stephane Guerin wrote:
>
> Could it be some setting on Adwords end? SOAP limitation or IP restriction 
> or anything else? I doubt that since it works well in dev, but we never 
> know. 
>
> We also created a service Web that wait for 2 seconds to test our threaded 
> calls and the HTTP connections limit doesn't seem to be a problem as all 
> requests get completed in around 2 seconds total (all at the same time 
> compared with adwords which is one after the other).
>
> Thanks for any idea.
>
> Stéphane
>
>
> On Wednesday, 3 April 2013 12:36:03 UTC-4, Stephane Guerin wrote:
>>
>> Hi Anash,
>>
>> Thanks for the answer. Unfortunately, I got no luck with this. The 
>> problem still occur. We also have in our web.config the max connections set:
>>
>>  
>> 
>> 
>>
>>  I checked all the settings in IIS or in the web.config. I really can't 
>> figure why it works in dev but not in production.
>>
>> Thanks,
>>
>> Stéphane
>>
>> On Wednesday, 3 April 2013 05:59:33 UTC-4, Anash P. Oommen (AdWords API 
>> Team) wrote:
>>>
>>> Hi Stephanie,
>>>
>>> Just wondering if there is a limit on the number of HTTP connections 
>>> your app can open on your production server? Your connectionmanager's 
>>> default limit of number of simultaneous HTTP connection is one common 
>>> reason why multithreaded report download can slow down in an unexplained 
>>> manner. See 
>>> http://stackoverflow.com/questions/2960056/trying-to-run-multiple-http-requests-in-parallel-but-being-limited-by-windows
>>>  for 
>>> a discussion.
>>>
>>> Cheers,
>>> Anash P. Oommen,
>>> AdWords API Advisor.
>>>
>>> On Wednesday, April 3, 2013 6:40:51 AM UTC+5:30, Stephane Guerin wrote:

 Hi,

 We have one weird problem with our ASP.NET MVC 4 application. Server 
 is a windows 2008 fully patched and up to date. We use AdWords API 
 DotNet Client 
 Library. 
 We ask for small reports, around 25 per batch.

 If we launch around 25 threads on our development server, they all 
 start in the same time and come back in about the same time too. As 
 expected.

 However, in our production server, when we launch the same app, all 
 threads start at the same time, but come back at 2 seconds interval each. 
 So instead of taking 2 seconds total, it takes around a minute. 

 Is there some option in IIS that is not enabled? Is there some 
 restriction based on our IP? We Googled the case a lot without success. 
 Nobody seems to have this problem with Adwords API but us. Plus the fact 
 that it works well in development tells us the problem is somewhere in our 
 production server.

 We can't find why. Any idea? 

 Thanks for any help,

 Stéphane

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

--- 
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.




Re: Concurrent requests not working on our production server

2013-04-03 Thread Stephane Guerin
Could it be some setting on Adwords end? SOAP limitation or IP restriction 
or anything else? I doubt that since it works well in dev, but we never 
know. 

We also created a service Web that wait for 2 seconds to test our threaded 
calls and the HTTP connections limit doesn't seem to be a problem as all 
requests get completed in around 2 seconds total (all at the same time 
compared with adwords which is one after the other).

Thanks for any idea.

Stéphane


On Wednesday, 3 April 2013 12:36:03 UTC-4, Stephane Guerin wrote:
>
> Hi Anash,
>
> Thanks for the answer. Unfortunately, I got no luck with this. The problem 
> still occur. We also have in our web.config the max connections set:
>
>  
> 
> 
>
>  I checked all the settings in IIS or in the web.config. I really can't 
> figure why it works in dev but not in production.
>
> Thanks,
>
> Stéphane
>
> On Wednesday, 3 April 2013 05:59:33 UTC-4, Anash P. Oommen (AdWords API 
> Team) wrote:
>>
>> Hi Stephanie,
>>
>> Just wondering if there is a limit on the number of HTTP connections your 
>> app can open on your production server? Your connectionmanager's default 
>> limit of number of simultaneous HTTP connection is one common reason why 
>> multithreaded report download can slow down in an unexplained manner. See 
>> http://stackoverflow.com/questions/2960056/trying-to-run-multiple-http-requests-in-parallel-but-being-limited-by-windows
>>  for 
>> a discussion.
>>
>> Cheers,
>> Anash P. Oommen,
>> AdWords API Advisor.
>>
>> On Wednesday, April 3, 2013 6:40:51 AM UTC+5:30, Stephane Guerin wrote:
>>>
>>> Hi,
>>>
>>> We have one weird problem with our ASP.NET MVC 4 application. Server is 
>>> a windows 2008 fully patched and up to date. We use AdWords API DotNet 
>>> Client Library . 
>>> We ask for small reports, around 25 per batch.
>>>
>>> If we launch around 25 threads on our development server, they all start 
>>> in the same time and come back in about the same time too. As expected.
>>>
>>> However, in our production server, when we launch the same app, all 
>>> threads start at the same time, but come back at 2 seconds interval each. 
>>> So instead of taking 2 seconds total, it takes around a minute. 
>>>
>>> Is there some option in IIS that is not enabled? Is there some 
>>> restriction based on our IP? We Googled the case a lot without success. 
>>> Nobody seems to have this problem with Adwords API but us. Plus the fact 
>>> that it works well in development tells us the problem is somewhere in our 
>>> production server.
>>>
>>> We can't find why. Any idea? 
>>>
>>> Thanks for any help,
>>>
>>> Stéphane
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

--- 
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.




Re: Concurrent requests not working on our production server

2013-04-03 Thread Stephane Guerin
Hi Anash,

Thanks for the answer. Unfortunately, I got no luck with this. The problem 
still occur. We also have in our web.config the max connections set:

 



 I checked all the settings in IIS or in the web.config. I really can't 
figure why it works in dev but not in production.

Thanks,

Stéphane

On Wednesday, 3 April 2013 05:59:33 UTC-4, Anash P. Oommen (AdWords API 
Team) wrote:
>
> Hi Stephanie,
>
> Just wondering if there is a limit on the number of HTTP connections your 
> app can open on your production server? Your connectionmanager's default 
> limit of number of simultaneous HTTP connection is one common reason why 
> multithreaded report download can slow down in an unexplained manner. See 
> http://stackoverflow.com/questions/2960056/trying-to-run-multiple-http-requests-in-parallel-but-being-limited-by-windows
>  for 
> a discussion.
>
> Cheers,
> Anash P. Oommen,
> AdWords API Advisor.
>
> On Wednesday, April 3, 2013 6:40:51 AM UTC+5:30, Stephane Guerin wrote:
>>
>> Hi,
>>
>> We have one weird problem with our ASP.NET MVC 4 application. Server is 
>> a windows 2008 fully patched and up to date. We use AdWords API DotNet 
>> Client Library . 
>> We ask for small reports, around 25 per batch.
>>
>> If we launch around 25 threads on our development server, they all start 
>> in the same time and come back in about the same time too. As expected.
>>
>> However, in our production server, when we launch the same app, all 
>> threads start at the same time, but come back at 2 seconds interval each. 
>> So instead of taking 2 seconds total, it takes around a minute. 
>>
>> Is there some option in IIS that is not enabled? Is there some 
>> restriction based on our IP? We Googled the case a lot without success. 
>> Nobody seems to have this problem with Adwords API but us. Plus the fact 
>> that it works well in development tells us the problem is somewhere in our 
>> production server.
>>
>> We can't find why. Any idea? 
>>
>> Thanks for any help,
>>
>> Stéphane
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

--- 
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.




Re: Concurrent requests not working on our production server

2013-04-03 Thread Zweitze
In your web.config (or app.config) file add:









and replace the 1000 with the maximum number of simulateous connections to 
a single host. Note the default is two (!), which explains the problems 
you're experiencing.


On Wednesday, April 3, 2013 3:10:51 AM UTC+2, Stephane Guerin wrote:
>
> Hi,
>
> We have one weird problem with our ASP.NET MVC 4 application. Server is a 
> windows 2008 fully patched and up to date. We use AdWords API DotNet 
> Client Library . We 
> ask for small reports, around 25 per batch.
>
> If we launch around 25 threads on our development server, they all start 
> in the same time and come back in about the same time too. As expected.
>
> However, in our production server, when we launch the same app, all 
> threads start at the same time, but come back at 2 seconds interval each. 
> So instead of taking 2 seconds total, it takes around a minute. 
>
> Is there some option in IIS that is not enabled? Is there some restriction 
> based on our IP? We Googled the case a lot without success. Nobody seems to 
> have this problem with Adwords API but us. Plus the fact that it works well 
> in development tells us the problem is somewhere in our production server.
>
> We can't find why. Any idea? 
>
> Thanks for any help,
>
> Stéphane
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

--- 
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.




Re: Concurrent requests not working on our production server

2013-04-03 Thread Anash P. Oommen (AdWords API Team)
Hi Stephanie,

Just wondering if there is a limit on the number of HTTP connections your 
app can open on your production server? Your connectionmanager's default 
limit of number of simultaneous HTTP connection is one common reason why 
multithreaded report download can slow down in an unexplained manner. See 
http://stackoverflow.com/questions/2960056/trying-to-run-multiple-http-requests-in-parallel-but-being-limited-by-windows
 for 
a discussion.

Cheers,
Anash P. Oommen,
AdWords API Advisor.

On Wednesday, April 3, 2013 6:40:51 AM UTC+5:30, Stephane Guerin wrote:
>
> Hi,
>
> We have one weird problem with our ASP.NET MVC 4 application. Server is a 
> windows 2008 fully patched and up to date. We use AdWords API DotNet 
> Client Library . We 
> ask for small reports, around 25 per batch.
>
> If we launch around 25 threads on our development server, they all start 
> in the same time and come back in about the same time too. As expected.
>
> However, in our production server, when we launch the same app, all 
> threads start at the same time, but come back at 2 seconds interval each. 
> So instead of taking 2 seconds total, it takes around a minute. 
>
> Is there some option in IIS that is not enabled? Is there some restriction 
> based on our IP? We Googled the case a lot without success. Nobody seems to 
> have this problem with Adwords API but us. Plus the fact that it works well 
> in development tells us the problem is somewhere in our production server.
>
> We can't find why. Any idea? 
>
> Thanks for any help,
>
> Stéphane
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

--- 
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.




Concurrent requests not working on our production server

2013-04-02 Thread Stephane Guerin
Hi,

We have one weird problem with our ASP.NET MVC 4 application. Server is a 
windows 2008 fully patched and up to date. We use AdWords API DotNet Client 
Library . We ask for 
small reports, around 25 per batch.

If we launch around 25 threads on our development server, they all start in 
the same time and come back in about the same time too. As expected.

However, in our production server, when we launch the same app, all threads 
start at the same time, but come back at 2 seconds interval each. So 
instead of taking 2 seconds total, it takes around a minute. 

Is there some option in IIS that is not enabled? Is there some restriction 
based on our IP? We Googled the case a lot without success. Nobody seems to 
have this problem with Adwords API but us. Plus the fact that it works well 
in development tells us the problem is somewhere in our production server.

We can't find why. Any idea? 

Thanks for any help,

Stéphane

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

--- 
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.