LL API uses LazyList, so PreparedQuery#asList is very fast. I modified the test code as follows: DatastoreService ds = DatastoreServiceFactory.getDatastoreService(); Query q = new Query("Bar"); PreparedQuery pq = ds.prepare(q); List<Entity> list = pq.asList(FetchOptions.Builder.withOffset(0).limit( Integer.MAX_VALUE)); list.size(); return list;
The result: The number of entities: 10000 low-level API:get: 1199 millis Slim3: 1238 millis JDO: 3298 millis Slim3 does not need runtime reflection for mapping between a entity and a model. The mapping logic is automatically created as the source code when compiling. so the speed of Slim3 is almost equal to LL API. Yasuo Higa On Tue, Jun 7, 2011 at 8:27 PM, Anders <blabl...@gmail.com> wrote: > I started by looking at JDO but after finding some info about potential > performance loss I wrote a simple wrapper abstract base class around a > low-level Entity object and then extended the base class into the data > classes I needed. Super light weight. :-) > > -- > 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/-/XzF3Q3MxcFVvbGdK. > To post to this group, send email to google-appengine@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-appengine@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.