If you consider for a moment that *all* of the rows for all of our applications are stored in one big logical BigTable, an extra 500 million is probably a drop in the bucket.
On the other hand, GAE has a limit of 1MB for any single entity. 3.5TB / 500M rows is about 7MB per entity, so that's not going to work. Also realize that 3.5TB will over $500/mo just for storage. Jeff On Mon, Apr 19, 2010 at 11:59 AM, sunsu <lylepr...@gmail.com> wrote: > Hi guys, > > I'm wondering if its possible for me to create a datastore on Google's > App engine that could feasibly grow to over 500 million rows > (entries). It would be all text (json blobs really), so I don't think > each entry would take up all that much space. I'm thinking if it were > to actually grow to be that big, It would be about 3.5 terabytes of > data (??). > > To give a little background: I'm thinking about making a game in which > the universe is made of a series of tilemaps. In order to create it at > the scale that I would like, I'll need to (eventually...because the > world would grow as people explored) store data for about 500 million > tilemaps :D. > > Would querying a datastore with 500 million rows even work relatively > quickly on Google's App Engine (assuming it was properly indexed)? > > Thanks for the input, > Sunsu > > -- > 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-appeng...@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-appeng...@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.
