drizzle-merge team mailing list archive

[Brian Aker <brian@xxxxxxxxxxx>]

You can toss what I put in or merge it. I am going to clean it up, but it is fine as is.

Sent from my iPad

On Aug 10, 2010, at 7:56 AM, Lee Bieber <lee.bieber@xxxxxxxxxxxxx> wrote:

> I can take this but am unclear on next steps. Do you want me to take what is in build and staging now and merge in Joe's patch, that is the only one that I see that is approved.
> 
> 
> On 8/9/10 11:18 PM, Brian Aker wrote:
>> Hi!
>> 
>> In Build/staging I have a patch right now which removes the keycache in favor of using the OS'es built in cache. It will need to be fine tuned. It would be nice to find out what the different machines output is, which I can grab from history.
>> 
>> This doesn't need to be pushed all the way through (and it would be fine to see it overwritten when I get up, assuming all of the email/reports still exist).
>> 
>> On the multi-tenancy front this removes all of the give/take/etc between different users, ie no single user can starve the IO from the cache to another user. There may be a performance penalty for this, I am unsure.
>> 
>> If someone wants to take them, I would take the two approved patches and merge them as one tomorrow. I would then take Pcrew's patches and do the same. Anyone want to grab this?
>> 
>> Cheers,
>> 	-Brian
>> 
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~drizzle-merge
>> Post to     : drizzle-merge@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~drizzle-merge
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of the
> individual or entity to which this message is addressed, and unless otherwise
> expressly indicated, is confidential and privileged information of Rackspace.
> Any dissemination, distribution or copying of the enclosed material is prohibited.
> If you receive this transmission in error, please notify us immediately by e-mail
> at abuse@xxxxxxxxxxxxx, and delete the original message.
> Your cooperation is appreciated.
>