Jeff, Which code is horrific?
I was going to load the Maxmind database into custom entities - so I don't see why it's a big deal if it's tough to load a split file a single time. After it's loaded into custom entities all of my geo queries would run against the datastore. Maybe I'm misunderstanding you. Krishna On Thu, Oct 6, 2011 at 9:33 PM, Jeff Schnitzer <[email protected]> wrote: > > Maxmind's database doesn't work this way. It's a flat file that gets > pulled entirely into RAM. The code is horrific and it's nontrivial to > make it read from anything other than a filesystem. We had to hack it > heavily just to read from a three-way-split file. > > The downside is that an app instance is slow to startup because it > needs to pull 30MB off of Google's incredibly slow filesystem. But > once it's running, lookups are pretty much instantaneous and > zero-cost. > -- 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.
