Good point.  Although in my case, I'm expecting to burn a lot of that $50 
migrating to HR once the new tool gets blessed.

I dug into the Google Storage and S3 options, and they both suck as solutions 
because the free tiers go away after year 1.  (Plus the authorization stuff is 
mind-numbingly complex.)

I think my plan right now is to sit tight.  The architecture I have looks like 
it should work when they fix the scheduler, and allow multi-threading in 
Python.  Switching to HR is going to be a huge PITA, because my use case is 
exactly the one that "eventual consistency" screws up (user posts a meeting, 
then expects to see it in the list of meetings; silly users).  But there's a 
gun to my head, so I guess I'll spend a weekend on it.  Sorry kids.

-Joshua

On Sep 2, 2011, at 12:31 PM, Barry Hunter wrote:

> There is another mitigating issue, that hopefully should be making
> this all academic anyway.
> 
> The $50 credit. That should cover costs for about 5 months on a *low
> taffic* website.
> 
> Which in theory should be enough for Multi-threading and the scheduler
> to be fixed* . At which case app can return to free quotas :)
> 
> 
> 
> * So that it will stick to one instance, even for a reasonable amount
> of traffic. I'm sure this is possible and feasible.
> 
> 
> (I'm tempted to signup for the multi-threading trail, just to see what
> sort of QPS a multi-threaded instance can handle. )
> 
> -- 
> 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.

Reply via email to