You shouldn't see any significant performance difference between the various java datastore APIs during normal operation. The JDO's classpath scanning may have a significant startup cost, but during execution the costs of RPCs and protocol buffer manipulation tend to dominate over any inefficiencies in object mapping.
On the other hand, third-party APIs offer shorter learning curves, better transparency, and easier access to native datastore features. And of course that startup hit can be a significant issue. Jeff On Fri, Oct 28, 2011 at 10:35 AM, Sheado <[email protected]> wrote: > Thanks Mat, > I'll check out Objectify. > > If any Googlers are reading this, it would be nice to add a section to the > docs clearly describing the performance differences between all of the apis > (low level api vs jdo vs jpa vs etc.) and maybe even between all of the > different languages. As it stands, with the current performance of my JDO > solution the costs of using appengine (due to high api cpu usage) would be > prohibitively high for me - it would have been nice to be able to guess that > right from the start. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/UPtK58TwQEMJ. > > 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-java?hl=en. > -- 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 [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-java?hl=en.
