Hi Jeff: Which version of Objectify you use? I am also happy with Objectify and it works for me at version 2.2. I start from GAE sample guestbook and build from there up with Objectify rather than with JDO. I have some issue with version 2.2.1 and do not have enough time to dig into it.
Thanks. Duong BaTien DBGROUPS and BudhNet On Sat, 2010-09-11 at 00:58 -0400, Jeff Schwartz wrote: > I am also using Objectify having switched from the low level api > because I wanted to codify my schemas (records) in pojos. I have to > say that I am very happy with both its api and performance. And the > Objectify commiters are really a nice bunch and very responsive when > having posted to their board. > > On Fri, Sep 10, 2010 at 6:37 PM, mscwd01 <mscw...@gmail.com> wrote: > Thanks for your replies. > > I took a closer a look at the requests using AppStats and > found I was > inadvertently querying entities in a loop. I rectified this > and now > request times are anything between 200ms and 450ms with the > average > request being about 350ms. I'm guessing this is not too bad? > > Also when checking the request time on the main dashboard, the > times > are always longer than that given by AppStats, why is this? > > Thanks again. > > On 10 Sep, 21:59, "Ikai L (Google)" <ika...@google.com> wrote: > > I think I can't type today. What I meant to say in my first > email was "there > > may be some performance benefit by switching to the > low-level API, but the > > overhead introduced by JDO/JPA should be minimal in terms of > queries and > > writes." > > > > > > > > > > > > > On Fri, Sep 10, 2010 at 1:50 PM, gholler > <georgehol...@gmail.com> wrote: > > > I'm on a team that built a JDO app engine project that was > fairly slow > > > and then built a similar project using Objectify. We were > very > > > pleased with the performance. We were also careful to only > index > > > fields we queried and also let Objectify doing caching for > us > > > automatically. > > > > > G > > > > > -- > > > 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-appeng...@googlegroups.com. > > > To unsubscribe from this group, send email to > > > > google-appengine > +unsubscr...@googlegroups.com<google-appengine%2Bunsubscrib > e...@googlegroups.com> > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-appengine?hl=en. > > > > -- > > Ikai Lan > > Developer Programs Engineer, Google App Engine > > Blog:http://googleappengine.blogspot.com > > Twitter:http://twitter.com/app_engine > > Reddit:http://www.reddit.com/r/appengine > > -- > 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-appeng...@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. > > > > > > -- > -- > Jeff > > > -- > 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-appeng...@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-appeng...@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.