Hi Amir,
There are a bunch of factors in query speed that can eventually
cause a timeout. Please contact me directly at [EMAIL PROTECTED] with a
few of the queries causing trouble and I'll see what I can find out.
Thanks;
— Matt Sanford (@mzsanford)
On Dec 2, 10:18 am, Amir Michail <[EMA
On Dec 2, 1:11 pm, Amir Michail <[EMAIL PROTECTED]> wrote:
> On Dec 2, 11:24 am, "Chad Etzel" <[EMAIL PROTECTED]> wrote:
>
> > I do OR queries through the search API all day long and they are always
> > blazingly fast from my perspective. Do you have some numbers you could
> > share regarding th
On Dec 2, 11:24 am, "Chad Etzel" <[EMAIL PROTECTED]> wrote:
> I do OR queries through the search API all day long and they are always
> blazingly fast from my perspective. Do you have some numbers you could
> share regarding the time it takes to do the query?
Queries of this form can be very slo
I do OR queries through the search API all day long and they are always
blazingly fast from my perspective. Do you have some numbers you could
share regarding the time it takes to do the query?
Also, having the client do it in their browser through javascript is also a
very easy and viable altern
Maybe you can do it in Javascipt on the Browser?
Richard
On Dec 2, 3:24 am, "Andrew Badera" <[EMAIL PROTECTED]> wrote:
> Which reinforces my "it's a GAE problem" stance ... GAE needs to accept the
> reality of the demands that will be placed on that system. Long-running
> operations against fore
Which reinforces my "it's a GAE problem" stance ... GAE needs to accept the
reality of the demands that will be placed on that system. Long-running
operations against foreign servers is one among many such issues.
On Mon, Dec 1, 2008 at 9:23 PM, Amir Michail <[EMAIL PROTECTED]> wrote:
>
> On De
On Dec 1, 9:08 pm, Amir Michail <[EMAIL PROTECTED]> wrote:
> On Dec 1, 8:15 pm, "Andrew Badera" <[EMAIL PROTECTED]> wrote:
>
> > The timeout I see as more of a GAE issue, not a Twitter one. You get what
> > you pay for, on both sides of that equation.
>
> It's not a CPU usage issue in the GAE. I
On Dec 1, 8:15 pm, "Andrew Badera" <[EMAIL PROTECTED]> wrote:
> The timeout I see as more of a GAE issue, not a Twitter one. You get what
> you pay for, on both sides of that equation.
It's not a CPU usage issue in the GAE. It's just that the request to
the twitter search API takes too long and
The timeout I see as more of a GAE issue, not a Twitter one. You get what
you pay for, on both sides of that equation.
No SLA, no billing from Twitter, beta and no billing on GAE's part ... and I
think we can agree, GAE hasn't been particular forthcoming nor cooperative
about what constitutes a tr
Hi,
OR search queries can take a long time and are causing lots of
timeouts with google app engine.
Amir
10 matches
Mail list logo
