My understanding is that with HRD you won’t have failed writes. Or no more
so than you would have otherwise. And if you like the last line of your
code can be the check to see if the Write completed.
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of
How would you check to see if the write was completed, with async there is
no guarantee when the write actually takes place?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.c
oogle-appengine@googlegroups.com] On Behalf Of Rohan Chandiramani
Sent: Thursday, January 19, 2012 1:55 AM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: Put_Async Use It
How would you check to see if the write was completed, with async there is
no guarantee when the
You always seem to be in a special GAE wonderland zone ;)
All operations can fail and...HDR or not...they fail sometimes. If a RDBMS
would fail as often as HDR on writes I would throw it away.
So my first question for such fire-and-forget async methods is: How do I
handle errors: even in RDBMS
: Thursday, January 19, 2012 2:13 AM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: Put_Async Use It
You always seem to be in a special GAE wonderland zone ;)
All operations can fail and...HDR or not...they fail sometimes. If a RDBMS
would fail as often as HDR on writes I
On Thu, Jan 19, 2012 at 5:13 AM, André Pankraz
wrote:
> So my first question for such fire-and-forget async methods is: How do I
> handle errors: even in RDBMS environment.
Keep in mind that async operations are not really "fire and forget".
They're "fire and forget until the end of your request"
om: google-appengine@googlegroups.com
> [mailto:google-appengine@googlegroups.com] On Behalf Of Rohan Chandiramani
> Sent: Thursday, January 19, 2012 1:55 AM
> To: google-appengine@googlegroups.com
> Subject: Re: [google-appengine] Re: Put_Async Use It
>
>
>
> How would you check
Subject: Re: [google-appengine] Re: Put_Async Use It
On Thu, Jan 19, 2012 at 05:13, Brandon Wirtz wrote:
> http://code.google.com/appengine/docs/python/datastore/functions.html
>
>
>
> Get Result will let you know if your Put has finished. That way you
> can do other things while the
Hm. This sounds a little counter intuitive. If you have threadsafe enabled,
the instance is able to process another request while a synchronous
datastore operation is in effect. The async ops should be most helpful when
you have threadsafe disabled. It sounds like there might be something else
o:google-appengine@googlegroups.com] On Behalf Of Robert Kluin
> Sent: Thursday, January 19, 2012 9:21 AM
> To: google-appengine@googlegroups.com
> Subject: Re: [google-appengine] Re: Put_Async Use It
>
> On Thu, Jan 19, 2012 at 05:13, Brandon Wirtz wrote:
>> http://code.google.c
obert Kluin
Sent: Wednesday, January 25, 2012 11:23 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: Put_Async Use It
Unless something has significantly changed with the 2.7 runtime, your output
isn't sent to the user until your request handling code has fully ex
Async everything will always save you instance hours. It doesn't matter if
you are threadsafe or not, the async operations allow you to perform a ds /
memcahce / url fetch in a background thread, which you can check on
whenever you want.
Async is extremely useful if you use it to perform "data
On Tue, Jan 31, 2012 at 7:43 PM, James X Nelson
wrote:
>
> PS - Anyone that doesn't actually call .get() on their futures to finalize
> your async operations could lose data, especially if the last operation in
> your method is an async put. Async operations started by your current
> processing t
There is a good chance the gains you saw are due to improved batching.
The other gains are probably from async, ie you being able to prepare
the data for your next put or fetch more data rather than waiting
around. If you're using Java, could also be multithreading gains.
As Jeff said, all RPCs
s
Cloud On A String Mastermind Group
-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Robert Kluin
Sent: Tuesday, January 31, 2012 11:10 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: Put_Async Use
ater Ops
>
> Cloud On A String Mastermind Group
>
>
>
>
>
>
>
> -Original Message-
> From: google-appengine@googlegroups.com
> [mailto:google-appengine@googlegroups.com] On Behalf Of Robert Kluin
> Sent: Tuesday, January 31, 2012 11:10 PM
> To: google-appeng
16 matches
Mail list logo
