Re: question about 2.20 db and stats

[Luis Villa <luis villa gmail com>]

On 8/5/05, Olav Vitters <olav bkor dhs org> wrote:
> On Fri, Aug 05, 2005 at 02:48:47AM -0400, Luis Villa wrote:
> > How hard is it to get a bugzilla-newer installation running, and to
> > update the DB (at least to seed it initially) from the live bugzilla?
> > I'm thinking I'd like to play with some bug stats stuff (and maybe
> > even reports porting), ideally while not completely knocking over the
> > live bugzilla with repeated applications of collect-stats.pl, which as
> > far as I can see means I need a local installation of at least the DB
> > and probably the whole shebang.
> 
> Collect-stats.pl doesn't slow down the database server (not noticably)..
> it just takes 1-2 weeks.

Uh... holy crap. That's terrible.

> I hope this is because of some missing indexes.
> If someone could optimize that... It uses the bugs_activity table
> heavily (and not very efficient).

I was looking at the code; it *does* look like it isn't optimal, but I
stared at it a few minutes trying to work out a better way and all the
approaches that came to mind looked suboptimal after a few more
minutes of thinking.

> Getting a bugzilla-newer is easy. Same as bugzilla-new, get a dump from
> bugzilla-new and run ./checksetup.pl. Oh, you do need to remove an
> index, see http://live.gnome.org/BugzillaUpgrade/UpgradeStatus
> (something like that).

OK.

> You want to update it regularly?

not necessarily; once I get the first dump I should have all the info I need.

> Not sure how to do that. Probably
> isn't too hard. Just dump every table except longdescs / attachments /
> bugs_activity completely and for the l/a/b_a tables use the time fields
> to get the selected records. The initial dump can be done using
> mysqldump, after that mysql + ssh portforwarding. Probably gets messy
> if you modify / create bugs locally.

Cool. Thanks, Olav.
Luis