On Wed, Jul 4, 2012 at 1:13 PM, Richard Watson <[email protected]> wrote: > Options I can think of: > 1) Using a bigger instance. You said it had some effect on startup > time? Rather pay more while you figure it out. Also, it might kick > you off any hot instances, if you don't fit on there anymore.
Definitely an option we have considered. As a bootstrapped startup with low revenue (so far), each $ counts... but if we keep having problems this will be the solution (assuming it solves the problem). At this point we have started instances on the new version. > 2) Seeing if you can log which specific parts of the startup is > slowing it down. Print stuff out using static initialisers if you have > to. If only I had a couple more days in the week :-) > 3) Pay the $500pm for premier support, if there's some way to do that > temporarily. Not sure whether you can afford to run it indefinitely, > but it sounds like this is costing you more than that at this point. > This is the most distasteful option, like paying tax for knowing how > to make your app start. Totally not in the budget, unfortunately. > What are the differences between your sandbox and prod? Just users, > or data as well? The startup time difference is independent of the datastore. I see this erratic startup problem with requests that only touch the urlfetch service (a https proxy for mapquest OSM tiles). The observed behavior difference between production and sandbox seems to be a function of the appid itself. Jeff -- 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.
