GAE (java) appstats - any way to see what the actual cache keys are for memcache calls? Why is every 5th or 6th seemingly-identical cache get taking way longer? Is there an actual code profiler if I upload my source?

[Keith Chima]

I know it's a lot of questions but thank you for your time. See the posted screenshot. All of these cache calls SHOULD be the same (I've chunked the cached objects into smaller objects, each has a pointer to the next object in the list), but there are some occasional time gaps between them making the call take longer and more importantly, some seem to take 75 ms instead of 2 ms for seemingly no reason. Any ideas? Can I actually see the cache keys of these individual cache get calls so I can troubleshoot?

Is there any way to see an actual code profiler so I can figure out what part of my code WITHIN a service call takes so long?

Thanks a ton!

[Les Vogel]

I may be misunderstanding your question, but Stackdriver > Logging >  Overview for any request should show you all GAE standard API calls for a given request, including Memcache.

Using Stackdriver > Trace > Trace list will let you drill down on individual requests and give you what is going on.  Once you understand what the API calls look like, you should  to use filters to find specific latencies for both Trace and Logging.

I'm not aware of any tool to iterate through memcache currently and I haven't tried to use the range commands with App Engine standard's memcache.

Les

--
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+unsubscribe@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/91abc7b7-74db-4bf5-b0ae-64590b3348af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

•  Les Vogel   •  Cloud Developer Relations   •  le...@google.com   •  +1-408-676-7023

[Keith Chima]

Thanks so much for your response Les. I love these tools, by the way. I was wondering if I could profile the specific stack code that's running to see what part of MY code is taking so long. Through appstats it seems like I can only see the GAE requests and everything else is a bit of a black box. I don't know if there's a way I can do that.

The other question is that it's difficult to see individual cache requests, some take 75 ms and some take 3 ms, and I can't see the cache key so it's difficult to troubleshoot.

Any recommendations?

Thanks,

-Keith

On Wednesday, December 20, 2017 at 8:52:44 PM UTC-5, Les Vogel wrote:

I may be misunderstanding your question, but Stackdriver > Logging >  Overview for any request should show you all GAE standard API calls for a given request, including Memcache.

Using Stackdriver > Trace > Trace list will let you drill down on individual requests and give you what is going on.  Once you understand what the API calls look like, you should  to use filters to find specific latencies for both Trace and Logging.

I'm not aware of any tool to iterate through memcache currently and I haven't tried to use the range commands with App Engine standard's memcache.

Les

On Tue, Dec 19, 2017 at 9:06 PM, Keith Chima <keith...@gmail.com> wrote:

I know it's a lot of questions but thank you for your time. See the posted screenshot. All of these cache calls SHOULD be the same (I've chunked the cached objects into smaller objects, each has a pointer to the next object in the list), but there are some occasional time gaps between them making the call take longer and more importantly, some seem to take 75 ms instead of 2 ms for seemingly no reason. Any ideas? Can I actually see the cache keys of these individual cache get calls so I can troubleshoot?

Is there any way to see an actual code profiler so I can figure out what part of my code WITHIN a service call takes so long?

Thanks a ton!

--
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/91abc7b7-74db-4bf5-b0ae-64590b3348af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Les Vogel]

Hi Keith,

You can look at the individual requests to see how long things take, and subtract out any serial requests you make and that's how long it's in your code.  You can, of course, add logging around areas that interest you to figure out how long they are taking.  (They should show up in the request log as well) or temporarily add log's using Stackdriver Debugger's LogPoint feature.  You can also use Guava's StopWatch and log the keys when the reference takes too long.

I'm not sure how to help you on debugging individual memcache requests, but if you ping the thread Jan 2, I'll try to find someone who knows.

Are you running with lots of threads?  (What are you concerned about that's not inside a request?)

AppStats isn't supported on Java 8.  I expect we'll have some additional profiling tools in the new year, but I'm not sure on a date.

Regards,

Les

To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscribe@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/e504f2e2-19c9-447e-ac84-2b38417c3ed0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.