While only somewhat related, I put in a request for a memcache feature
that allows data to prioritised, with higher priority data never
evicted by lower priority data. Doesn't solve the entire problem of
eviction, but at least lets you happily cache as much as you want at a
lower priority and not c
>> If you can tolerate additional latency, why not store data into the
>> datastore?
Because it's expensive? :) There's a big difference between making a
100ms put to datastore every request and making one every n requests.
Requests with that higher latency may be tolerable from a end-user's
POV
We're moving into a middle ground between Memcache and the datastore. If you
can tolerate additional latency, why not store data into the datastore? You
should not design assuming memcache will preserve critical data. Don't store
anything in memcache that you cannot recover if evicted, even if your
It would, but depending on the extent of that latency it might be a
reasonable trade off for reliability. I've an app that could
definitely tolerate some % of memcache saves being higher latency if
it guaranteed I didn't lose data.
The option of a silent background put() to the datastore upon evic
On Apr 15, 9:48 am, peterk wrote:
> It'd be great if memcache could throw a warning or error upon a put to
> memcache, if that put will cause an eviction of another value, and ask
> you to retry your put with a token to confirm you're OK with the
> eviction.
It's a cache. That would add annoyi
Are there benchmarks available for memcache reliability on GAE?
It'd be great if memcache could throw a warning or error upon a put to
memcache, if that put will cause an eviction of another value, and ask
you to retry your put with a token to confirm you're OK with the
eviction. The equivalent of
On Apr 14, 10:23 pm, Timofey Koolin wrote:
> You can write your log and other tasks to memcache. In tasks or by
> cron you can read your meny data from memcache per time and write to
> datastore.
...if you don't mind losing your data sometimes.
--
You received this message because you are sub
You can write your log and other tasks to memcache. In tasks or by
cron you can read your meny data from memcache per time and write to
datastore.
On 14 апр, 22:42, Harlan Crystal wrote:
> I have removed a number of tasks to avoid hitting the limit, but what
> should I plan to do in the future?
>
I have removed a number of tasks to avoid hitting the limit, but what
should I plan to do in the future?
We often receive ~1M organic hits per day. With a limit of 1M tasks
per day, I can't even spawn off one task per hit to take care of
background processes (logging, updating sharded counter sta
