app-engine-ndb

I think there is a memory leak in the ndb library but I can not find where. Is there a way to avoid the problem described below? Do you have a more accurate idea of testing to figure out where the problem is? That's how I reproduced the problem : I created a minimalist Google App Engine application with 2 files. app.yaml : application: myapplicationid version: demo runtime: python27 api_version: 1 threadsafe: yes handlers: - url: /.* script: main.APP libraries: - name: webapp2 version: latest main.py : # -*- coding: utf-8 -*- """Memory leak demo.""" from google.appengine.ext import ndb import

Say I have a picture gallery and a picture could potentially have 100k+ fans. Which ndb design is more efficient? class picture(ndb.model): fanIds = ndb.StringProperty(repeated=True) ... [other picture properties] or class picture(ndb.model): ... [other picture properties] class fan(ndb.model): pictureId = StringProperty() fanId = StringProperty() Is there any limit on the number of items you can add to an ndb repeated property and is there any performance hit with storing a large amount of items in a repeated property? If it is less efficient to use repeated properties, what is their intended

Suppose I initially create an ndb.Model and wanted to change a field's ndb property type (e.g. IntegerProperty to StringProperty), but wanted to cast the current data stored in that field so that I don't lose that data. One method would be to simply create a new field name and then migrate the data over with a script, but are there other more convenient ways of accomplishing this? For example, suppose I had the following model: class Car(ndb.Model): name = ndb.StringProperty() production_year = ndb.IntegerProperty() And I stored an instance of the entity: c = new Car() c.name = "Porsche" c