In a separate thread, someone from Google confirmed that they compile all the files from scratch with each load.
Speeding up cold starts is clearly the best solution, but I don't know how much time pre-compiling would save. Paying for warm instances may help, but because anyone can auto-ping every second, the tragedy of the commons will still proceed to its inevitable conclusion, causing tremendous thrashing. On Oct 22, 6:05 am, bFlood <bflood...@gmail.com> wrote: > agreed, this a catch22 for low request sites. pinging only goes so far > and seems completely wasteful (for everyone) > > I'd love to know if they precompile python modules (and if not, there > must be a good reason why) > paid for warm instances - yes! > > cheers > brian > > On Oct 22, 7:25 am, ted stockwell <emorn...@gmail.com> wrote: > > > On Oct 21, 10:31 pm, Devel63 <danstic...@gmail.com> wrote: > > > > I see only 2 ways out: > > > Another way would be for Google to charge to keep applications warm. > > Amazon has a similar feature where you can pay extra to reserve EC2 > > instances to make sure that the instance are always available. > > Keeping apps warm is quite resource intensive, so I don't see how > > Google could not charge for it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
