launchpad-dev team mailing list archive

[Stuart Bishop <stuart.bishop@xxxxxxxxxxxxx>]

On Wed, Aug 4, 2010 at 9:46 AM, Robert Collins
<robert.collins@xxxxxxxxxxxxx> wrote:

> Doing this will immediately close a half-dozen bugs, and focus our
> timeout and performance efforts closer to the actual source of our
> problems.

Which bugs? The only open ones I'm aware of are feature requests which
I don't think are on anyone's radar to address.

I'm not sure why turning the facility off will help peoples focus -
memcached was never about stopping timeouts and this has been
repeatedly stressed. Using the facility will slow down initial loads,
and may improve the median page load time. It won't fix timeouts. It
may reduce the frequency of timeouts. The memcached infrastructure is
about improving scalability and overall performance, and throwing away
our 24% hit rate seems rather pointless (better rate than I was
expecting actually, but I guess the places it is being used have been
specifically targeted). The same rationales for turning off would be
applied to turning off Squid, which fills pretty much the same role
but more so by caching 100% of our unauthorized access.

Turning it off is also rather problematic for foundations scalability
and performance work - it is the most likely replacement for OAuth
nonce and Session storage.

> In the future, I would like to be able to turn memcached back on in a
> more scaling role, which is what it is designed for and great at.




-- 
Stuart Bishop <stuart@xxxxxxxxxxxxxxxx>
http://www.stuartbishop.net/