The app is relatively quick. The cause of the instance hours is that the app has a cron job which runs once every two minutes. It returns quickly, but it keeps the instance pegged all day long. So, low-cpu but high instance-usage.
On Fri, Sep 9, 2011 at 2:40 PM, Steve Sherrie <st...@wasteofpaper.com> wrote: > But in all seriousness, you're saying it would be a gargantuan feat to > improve those figures? > To get such a extreme difference (3min cpu => 28+ frontend instance hours) > you're probably heavily relying on synchronous RPCs in some way, and that's > exactly the kind of thing that can be made substantially more cost-efficient > under the new billing with relatively little effort. Is this the case? > > Stove (I saw bridesmaids yesterday) > > -- > 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/-/xNhQScOpLG4J. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
