It's somewhat difficult to tell from your description what the cause of the
slowness might be. Just to clarify, in Stackdriver Traces, the latency for
a given request appears to be the time taken from when the client request
is received and when the server response is sent. Is this in fact the
hi NIcholas,
its the same request that is taking different time to complete the task, in
my case two users are accessing same row at the same time and the row it
self has a size of 100KB ,its a turn based game, so first turn it works
perfectly , second turn you will get this delay of at least 3
Thanks for providing a little more information. 3 to 4 minutes is indeed
strange but I cannot reproduce this latency. For testing, I created
100,000 rows of text columns. Then sent over 100 requests to an App Engine
instance that retrieves a single row (always the same one) and updates it.
I
No I haven't used Stackdriver , i will use now and update you. In my case
request processing works perfectly with small data, it has a problem when
its working with large data and manipulating it. any limitation for app
engine in handling large amount of data?
On Thursday, August 4, 2016 at 2:1
What are you doing with "large data"? if you are loading large amounts of
data into ram, processing it and then writing it back to the database it
will be slower then smaller transactions. There is a maximum read/write
throughput and a max CPU speed on your DB and instances.
On Wednesday, Aug
Good day Anoop,
I hope your testing is going well. To help test latency, I would strongly
suggest you consider the following:
- What the average size of a client request payload sent to your App
Engine instances?
- How many of these requests are you seeing per second or minute during
