On Sat, Jul 16, 2011 at 1:14 AM, Jeroen Vermeulen <j...@canonical.com> wrote: > Thank you so much for pushing this through!
My pleasure! > There _is_ an immediate payoff: your db patch gets deployed much faster. > We've been aching for this kind of flexibility. Thats the promised payoff; its not immediate *yet* because Stuart and I haven't gotten the all the deployment bits together :). > We'll learn how to write incremental patches. Meeting the 15s goal on a > cold database will be hard though, since we can't easily reproduce results > or try out tweaks. It might help if we could break a slave out of > replication to time a DB patch against a realistic cache. I should clarify then - what I mean by cold is more of a 'no cheating' - no running it twice on qastaging within a transaction and then taking the best time. Run it once, take the time. This is to get as close as we can approximate to actual-behaviour on prod (though we should expect prod to be consistently faster :)). -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
