Re: [Bacula-users] *Extreme* low MySQL performance when prunnig or purging jobs/volumes

[Christoph H. <em...@ch...>]

On Tuesday 25 October 2005 15:08, Volker Sauer wrote:
> Yes, and that's the solution! The missing index on JobId make the SQL
> with "... where JobID=...." painfully slow!
> I checked the source and the debian package and this index is included
> by default. I have no idea why it's missing on my database. I'm creating
> it right now (takes some time)!

I'll try that, too. I was pretty annoyed by the low speed, too. Restoring
files from a full backup and two incremental backups takes 10 minutes to
show me the list of files (800,000 files in backup).

But where in the Debian package (I assume you mean Sarge) did you see
that an index over "JobId" is being created? I just found:

/usr/share/bacula-director/make_mysql_tables

And it just reads:

# Possibly add one or more of the following indexes
#  to the above File table if your Verifies are
#  too slow.
#
#  INDEX (JobId),
#  INDEX (PathId),
#  INDEX (FilenameId),
#  INDEX (JobId, PathId, FilenameId)

So that's just a suggestion.

If it were really a bug in the Debian package I'd like to report it.

Admittedly at the time I installed Bacula there was still the annoying bug
that broke the installation when using the MySQL backend
(http://bugs.debian.org/312329). So I may have used a different
installation routine than you.

 Christoph
-- 
~
~
".signature" [Modified] 1 line --100%--                1,48         All