> I recently played with the lower level API as well. Some of the > features are not available in JDO, like reserving a key before > committing a new object.
Yes, we wanted to get access to those. Specially, the "create several keys at once" and "persist several entities at once" are great, we combined those to implement the put(Iterable<Object>) method. > Just wondering do you have any performance profiling stats? I also > feel like JDO is overkill, but I couldn't justify porting all JDO > objects to another simple type without knowing how much cpu_ms it will > save. Nope. I can tell you that deployments are much faster and the typical stack trace has dropped from 10-15 lines to 3. And, of course, class enhancements are no longer necessary. > Also, do you keep track of which field is dirty and avoid committing > unmodified fields? I believe this is important to minimize api_cpu to > avoid unnecessary index updates. I don't think you can do that (please someone correct me if I'm wrong). If you omit any field while putting an entity, you lose those fields in the persisted entity because it's schema-less. What you can do is disable field checks (required fields while saving, existing fields while querying) to make it faster in production, if you feel confident in your QA. Regards, Nacho. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
