We're going to a trade conference next week to demo our app, but we can't afford $5000 for an Internet connection. "No problem," we thought, "we'll just demo it off of the development appserver."
So we're trying to work around the sluggishness with which the dev appserver responds to requests. Yet no matter what the request (a tiny static file, an immediate HTTP response through Django, a memcache hit, whatever), debug or not, with tons of data or no data in the datastore, every response takes 1.5 seconds. Brutal. I finally figure out why the development appserver is so slow (and has always been getting slower, I now realize): on every request, it's spending nearly 1.5 seconds parsing our long local datastore history file, even if the request doesn't explicitly query the datastore. I hadn't even thought of this; we manage the size of the datastore file, but apparently the history file had never been cleared. It had grown to 813 KB with 11315 queries (and that's from my machine alone). So yeah, that was it. Everything runs nigh-instantly now. I haven't seen any references to this problem elsewhere, or any warnings that a long history file can impact performance, so maybe this'll help someone avoid our fate. Perhaps it can be mentioned in the docs. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
