Hi Anirban,

While questions about best practices, optimization, and the like, are on 
topic for Google Groups, we need a LOT more context into your application 
to be able to provide ANY kind of answer here. At the time of reading, I'm 
not even sure if you're talking Datastore or CloudSQL. In any case, not 
knowing what models you have, what your application does, where do you want 
lower latency, what's done backend or frontend, this is literally 
impossible to answer.

I can give generic tips for now, like to use "getByKeys", since they don't 
cost reads. You could also make use of memcache for non-critical data that 
is updated enough (but memcache can flush before you end up saving it, so 
make sure this IS non-critical). But that's assuming you're discussing 
Cloud Datastore (in which case I would suggest you give this article 
<https://cloud.google.com/appengine/docs/java/datastore/indexes>).

In any case, provide a bit more context into your question, and either 
myself or someone from the community will be happy to help.

Cheers!



On Monday, September 21, 2015 at 3:23:36 AM UTC-4, Anirban Silsarma wrote:
>
> How can i minimize read write operation, and how can I understand how much 
> read and write operation has occurred in per transaction?? 
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/e5af0fea-7f8f-427e-ae79-fbddbd4558c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to