Jeff, This made me smile as we did the exact same thing. Split the maxmind database in 3 and reconstituted the file in code.
We initialise the database in a warm up task so it gets loaded into memory. It's quite speedy after that (but it does take up a chunk of memory) cheers James On 7 October 2011 08:28, Jeff Schnitzer <[email protected]> wrote: > No point. It fits into a frontend instance - currently occupying around 108 > MB. > > I'd post my code that reconstitutes the three part file into one, but > it's pointless with the 30MB file limit raise around the corner. > > Jeff > > 2011/10/6 Ronoaldo José de Lana Pereira <[email protected]>: >> Jeff, >> >> Does your aproach plays well as a backend? >> >> -Ronoaldo >> >> -- >> 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/-/tggusylTQdsJ. >> 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. >> > > -- > 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. > > -- 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.
