launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #05112
Re: Going all the way or the proper way to create work for others
On Sunday 10 October 2010 03:02:38 Robert Collins wrote:
> There were various OOPSes and timeouts related to the refactoring -
> while it was done in a compatible fashion, these OOPSes were caused by
> the refactoring:
> - two schemas at once with redundant data and tables, mismatched DB
> and code constraints (AIUI once the migration is finished the looser
> DB schema will be correct).
This was caused by our attempt to try and use the Job system API and schema.
As I've mentioned before, this was an extremely poor choice and I wish I'd
pushed back harder on those asking for it.
However, that's got nothing to do with handovers.
> - poor query performance related to this
I don't recall this (although my memory does suck). Can you give any example
please?
> As a result, I really wouldn't call the hander to other teams as an
> 'optional' : until the transition is finished (IIRC it isn't yet
> finished, pending a translations DB change going live, we still have
> things in progress), we suffer performance
Can you explain the poor performance? (if not the same as above)
Cheers
J
References