Thanks Nick - hoped this was the case, just haven't seen it confirmed!

Jan

On Jun 13, 10:15 am, "Nick Johnson (Google)" <[email protected]>
wrote:
> Hi Jan,
>
> Because memcache is entirely in-memory, and quite straightforward, it's
> extremely fast. A memcache server can typically handle thousands of QPS -
> more than your app is likely to see - so you're quite safe not sharding
> memcache calls.
>
> -Nick Johnson
>
>
>
> On Sat, Jun 12, 2010 at 10:28 PM, Jan Z <[email protected]> wrote:
> > Hello - I'm looking for some advice on performance of memcache incr()
> > operations.  I assume that these can become a bottleneck when a lot of
> > traffic hits and need to get sharded, the question is what is "a lot".
>
> > I'm using memcache incr() for counting specific event types and would
> > like to understand if this is an issue that's likely to affect my
> > app.  I have no problem losing the stats occasionally (during
> > maintenance periods, etc.)
>
> > Any thoughts on what this number might be, even in terms of an order
> > of magnitude??
>
> > Thanks!
>
> > Jan
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<google-appengine%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. ::
> Registered in Dublin, Ireland, Registration Number: 368047
> Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number:
> 368047

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to