Connections should be short-lived, so from an absolute perspective,
yes. From a practical perspective, if your requests are designed to
execute as quickly as possible, it'll take a long time before this
affects application performance. Note that static assets do not count
against this limit.
On Th
On Mar 2, 6:05 am, "Nick Johnson (Google)"
wrote:
> Actually, the default limit is 30 active requests.
>
> -Nick Johnson
Hi Nick,
Will Google make "simultaneous dynamic requests limit" be part of a
billable option in the future, such that applications can pay to have
this limit increased?
Also,
bump
On Mar 3, 7:23 pm, Eli Jones wrote:
> Heh, yes.. I printed out your Java and it seemed perfectly fine after
> reading through it several times... But Java is just wayy to busy
> looking for my tastes.
>
> Good luck getting some clarification on what's happening with this.
>
> On 3/3/10, Gary
Eli,
Python as usual is sooo much more elegant than java.
I confirmed your test results on a billing enabled appspot.
Cheers, Gary
On Mar 2, 9:57 pm, Eli Jones wrote:
> I did my own testing in python. And, I definitely couldn't get 30
> simultaneous requests to work.
>
> This was done on a te
Eli,
Python as usual is sooo much more elegant than java.
I confirmed your test results on a billing enabled appspot.
Cheers, Gary
On Mar 2, 9:57 pm, Eli Jones wrote:
> I did my own testing in python. And, I definitely couldn't get 30
> simultaneous requests to work.
>
> This was done on a te
I did my own testing in python. And, I definitely couldn't get 30
simultaneous requests to work.
This was done on a test app that does not have Billing Enabled.. so not sure
if that affects the Dynamic Request Limit.
Either way, it seems that for this test, the effective Limit was 16
simultaneou
Hi All
> Actually, the default limit is 30 active requests.
> I can only reach 10 active requests without error.
Same here. I've been checking the instance count on my Task Queue
servlet and I've never seen it exceeds the 10 instance limit. There
are two other App Engine developers on my twitter
Thanks Gary. I'll run this code through my mental debugger to see if
anything pops out.
I'm going to write my own more simplified test where I just create some
python code that hits the request handler.. and once it gets a response.. it
just tries again (For maybe 10 - 20 times in a row.)..
Then,
Eli,
You have the python request server.
Here is the java client:
You'll have to get the libraries yourself.
Cheers, Gary
import java.util.ArrayList;
import java.util.concurrent.Callable;
import java.util.concurrent.ExecutionException;
import java.util.concurrent.ExecutorService;
import java.uti
Eli,
You have the python request server.
Here is the java client:
You'll have to get the libraries yourself.
Cheers, Gary
import java.util.ArrayList;
import java.util.concurrent.Callable;
import java.util.concurrent.ExecutionException;
import java.util.concurrent.ExecutorService;
import java.uti
Actually, 4 threads was before we optimized server side, and set up
the test environment.
I have a tarball, about 8mb, with the test environment. (django and
libraries, grrr)
What is the best way to post this? I don't see any file attachments
on groups.
Cheers, Gary
On Mar 2, 8:23 am, Eli Jone
But that's the point. I can not reach 30 active requests.
I can only reach 10 active requests without error.
Any ideas on how I can debug this?
Cheers, Gary.
On Mar 2, 7:05 am, "Nick Johnson (Google)"
wrote:
> Hi,
>
> On Tue, Mar 2, 2010 at 1:54 PM, Wooble wrote:
> > The 500 requests per se
Are these threads you're using (at this point, it really seems like you
should post some simplified code to illustrate the issue at hand) waiting
for their response before trying to get again?
Posting some code to help recreate this issue will lead to a much faster
resolution.. as it stands.. I ju
But that's the point. I can not reach 30 active requests.
I can only reach 10 active requests without error.
Any ideas on how I can debug this?
Cheers, Gary.
On Mar 2, 7:05 am, "Nick Johnson (Google)"
wrote:
> Hi,
>
> On Tue, Mar 2, 2010 at 1:54 PM, Wooble wrote:
> > The 500 requests per se
Hi,
On Tue, Mar 2, 2010 at 1:54 PM, Wooble wrote:
> The 500 requests per second number relies on the probably-unreasonable
> assumption that each request can complete in ~75ms. Deliberately
> making your requests take a whole 3 seconds each is, obviously, not
> going to work. You can only have
The 500 requests per second number relies on the probably-unreasonable
assumption that each request can complete in ~75ms. Deliberately
making your requests take a whole 3 seconds each is, obviously, not
going to work. You can only have 10 instances active at a time by
default; if the pages you'r
Hi Nick,
Hmm, I was running tests on a billing enabled appspot today. 100
requests/test.
10 threads getting a URL with a 3 second sleep (to emulate
computation) on appspot, was the most I could get without getting 500
errors.
If I raised the thread pool beyond 10, I started getting errors??
Th
17 matches
Mail list logo
