No, there is no way to make it more precise. There will always be some delay and variation. Think of the eta / countdown as a 'polite request' to execute the task around that time.
If you need precision, Tim's backend suggestion may be your best bet. There are probably other solutions using cron as well. Robert 2011/8/17 Sébastien Tromp <[email protected]>: > Precision: in local environment, everything is fine. I have a small > difference (around 30 ms) between the time at which the task executes and > the time it is supposed to execute. > When deployed on GAE, the differences are usually around 10-15s, sometimes > up to a minute and a half. > > 2011/8/17 Sébastien Tromp <[email protected]> >> >> Hi again, >> I have it working ok for now, not using a backend at the moment (still >> waiting to see whether I really have the need for it). >> However, the countdownMillis() or etaMillis() look rather unreliable (I >> had tasks that waited for around 100s before being executed, while the >> countdown was around 10s). The queue is hardly full (at most 5-6 tasks in >> it, none of which requires heavy processing). >> Is there a way using appengine to have a more reliable execution of >> delayed events? >> Thanks, >> -- >> Sébastien Tromp >> >> 2011/8/10 Sébastien Tromp <[email protected]> >>> >>> Hi Tim, >>> Thanks for your hindsight. I think I'll first try and play with tasks >>> queues and see how it goes, and then study how to integrate a backend later >>> on when I'm more familiar with all of this. >>> Thanks again :) >>> -- >>> Sébastien Tromp >>> >>> On Wed, Aug 10, 2011 at 12:34 PM, Tim Hoffman <[email protected]> wrote: >>>> >>>> Hi Sébastien >>>> Off the top of my head >>>> >>>> The resident backend could maintain its own wall clock time, and sit in >>>> a busy loop checking for actions to perform via memcache. >>>> It could then put updates back into memcache, the front ends can be >>>> keeping an eye on the gamestate updates in memcache (tasks maybe, or the >>>> backend could signal front ends via xmpp) >>>> Just some thoughts. >>>> T >>>> >>>> >>>> -- >>>> 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.com/d/msg/google-appengine/-/1Ln8GBqXiucJ. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]. >>>> For more options, visit this group at >>>> http://groups.google.com/group/google-appengine?hl=en. >>> >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
