I had spent most of the night wondering about task queue's apparent inefficiencies under Scheduler, and had planned to open a topic related to it, but then read Joshua's post.
THIS point made by Joshua is THE HEART of the issue:'...it's a lot more trouble than just having a way to say to the scheduler, "run these when you have an idle instance with nothing better to do," or "DO NOT spin up an instance just to handle this task"...' As Joshua suggests, there is likely a great deal of optimization within an instance obtainable by elegantly utilizing TQs. Scheduler today, however, seems quite inelegant (and unfortunately may remain that way because instance optimization is markedly revenue and profit negative for GAE). At this point, I would like to suggest that GAE employ a consultant who is an expert with systems modeling with iThink. The current opaqueness and complexity of Scheduler are an ideal situation for this type of systems analysis.** Link: http://www.iseesystems.com/softwares/Business/ithinkSoftware.aspx Please Google, can you give us some more help here. Thanks, stevep ** not at all affiliated with iThink, but have developed some financial analyses using iThink back in the day when I worked for HP. It really is a great tool for situations like this, and you guys will certainly find that there are some very experienced and capable consultants who will do great things for you without too much time needed from GAE personnel. -- 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.
