On Friday 16 September 2005 14:02, Daniel Weuthen wrote:
> > > > I had the same problems with Jobs which have more than 680000 files
> > > > and mysql as database. After putting an index on JobId in the File
> > > > table I got an enormous speed up:
> > >
> > > I just tried this and the speedup is amazing. Getting to selection of
> > > individual old files for a user now takes less than 5 minutes, vs more
> > > than an hour previously.
> >
> > This is surprising because I always understood that a multiple index
> > (JobId, PathId, FilenameId) was equivalent (actually better) than one
> > only on JobId.
> >
> > Could you tell me what DB you are using MySQL, ...?
>
> mysql Ver 12.22 Distrib 4.0.24, for pc-linux-gnu (i386)
>
> as released in debian sarge
>
> > and confirm what
> > indexes you had before and after your change?
>
> previously there was an index called FilenameId which included the columns
> FilenameId and PathId only.
Are you running on 1.36.3? If so, this is strange since the default table
setup for 1.36.3 includes an index on JobId in the File table.
>
> I just added the index JobId including only JobId because when bacula is
> building the filelist the where statemant looks for matching JobId's most
> of the time.
>
> > If simply adding a single index on JobId to the File table makes such an
> > amazing difference in speed, I definitely want to ensure that 1.38 is
> > released that way.
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
