Hey Jeff, A post like yours should be made to the Public Issue Tracker (linked <https://code.google.com/p/googleappengine/issues/list> in a previous post), along with technical details of the exact queries, what you expected, what you observed instead, and any information (code snippets, a complete repository link) needed to allow reproduction and observation on another machine (one of our machines). This would be the best way to make sure the issue is seen by the Appstats maintainers or someone close to such.
Regards, Nick On Sunday, January 31, 2016 at 4:03:48 AM UTC-5, Rahul Tongia wrote: > > Hi Jeff and Nick, > > I am facing the same problem regarding projection query costs. I had > performed the same projection call on my local machine with appstats using > both Objectify (with hybrid as false) and native Datastore API. In both > cases, I got same result in terms of Read counts. It was 896 reads where as > I was expecting 1 read with 895 small ops. > > To me, the problem looks like either in Appstats for Java where it is not > able to estimate the projection query entity reads as small ops or the > Projection query itself is broken in terms of costs. Atleast, Objectify > seems to be not causing this issue. > > I will check in production, how my read costs get affected with this > change. > > Nick could you please check with Appstats team (if any one is maintaining > it) if this is an Appstats issue? > > Thanks, > Rahul > > > On Tuesday, December 22, 2015 at 7:07:55 PM UTC+1, Nick (Cloud Platform > Support) wrote: >> >> Jeff's analysis is on-point here. It seems certainly possible that Ofy >> could be transforming the query. The only way is to test, and the methods >> to do so have been given. If this turns out to be a Datastore problem, >> rather than just Ofy, a post should be made to the Public Issue Tracker. >> Someone from Cloud Platform Community Support will triage the issue shortly >> after it appears. >> >> On Saturday, December 19, 2015 at 10:01:06 AM UTC-5, Jeff Schnitzer wrote: >>> >>> Run the equivalent query with the low-level API. If it produces the same >>> unexpected results, it's Google's issue. If it fixes the problem, it's >>> mine. Other than a potential hybridization issue I can't imagine what >>> Objectify could be doing wrong since it's just adding projections to an >>> underlying low-level Query object. >>> >>> Jeff >>> >>> On Fri, Dec 18, 2015 at 5:50 PM, NAyAN Jain <gamern...@gmail.com> wrote: >>> >>>> No I haven't used the cache annotation but still the cost and >>>> datastore read are same as a normal query. >>>> I am looking for a way to reduce read operations. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Google App Engine" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to google-appengi...@googlegroups.com. >>>> To post to this group, send email to google-a...@googlegroups.com. >>>> Visit this group at https://groups.google.com/group/google-appengine. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/google-appengine/604573fe-8f5b-4763-a742-358eef9f06ca%40googlegroups.com >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/39ce5398-fcaf-4478-97df-a3eaccbbf940%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
