Hi Kim,
Can you please provide your app ID?
Also, how are you accessing your app? Only via appspot.com, or also via a
Google Apps domain you've mapped to the app? The more details you can
provide about your load testing - especially the actual code - the easier
this will be to diagnose.
-Nick
Hi Kim,
Can you please try flushing your memcache and running your tests again? The
issue should now be fixed.
-Nick
On Tue, Jun 23, 2009 at 2:42 PM, Kim Riber kimsteenri...@gmail.com wrote:
Yes. There is no other activity when running step 3.
The two values I get back, are some of the last
Just made another test, to confirm the behavior I see.
This example is much simpler, and simply has 10 threads writing random
values to memcahce to the same key.
I would expect the last value written to be the one left in memcache.
When afterwards, having 4 threads reading 10 times from that same
Hi Kim,
It's not clear from your description exactly how you're performing your
tests. Without extra information, the most likely explanation would be that
you're seeing a race condition in your code, where the key is modified
between subsequent requests to the memcache API.
Also, are you
Hi Nick
I run the test in 3 steps (with half a minute in between):
1. Heavy load process to spawn appinstances
2. Write a lot of random values to the same key
3. Read the key from multiple threads.
I can repeat 3rd step, and still get the same result (mostly 2
different values)
It seems like I
To clarify a bit:
one thread from our server runs one loop with a unique id.
each requests stores a value in memcache and returns that value. In
the following request, the memcache is queried if the value just
written, is in the cache.
This sometimes fail.
My fear is that it is due to the
