I don't know much about Slim3 but I just migrated from JDO to the native API, and I can say that the performance improvement was in many cases dramatic. I was assured many times that JDO's overhead is insignificant, but that hasn't been my experience. I chalk it up to JDO's reliance on reflection, and also to the fact that using JDO produces some bad datastore-habits under the hood. I question JDO's appropriate usage of batch datastore operations, which can produce a significant performance boost. Also, the fact that objects must be retrieved before they are updated with JDO can make things a lot slower.
The native API is IMO simple, and powerful - I wish I had made my own wrapper tailored specifically for my app from the get-go, and I encourage everyone to do the same. On Jun 7, 12:24 pm, Anders <[email protected]> wrote: > I doubt that the difference can be that large. The performance test code > uses the low-level PreparedQuery#asList call. The question is if the list > (List<Entity>) contains entities loaded with data or if the list returned > has a lazy loading implementation so that the actual data from the datastore > only gets loaded when entity properties are accessed. -- 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.
