hi,
bweb Statistics -> Backup Timing is nice feature,
but sql query behind is slow on mysql.
recently my browser timed out on btime.pl.
currently we are running 50 nightly jobs and Job table contains
about 27000 jobs (CentOS 5.5, git branch Bacula-5.0, mysql-5.0.77)
i fixed the timeout problem by creating an Index on Job.StartTime,
now the timing sql query from btime.pl (see below) runs much faster.
maybe there are better ways to optimize, but comparison on
time fields without index are really slow on mysql.
please think about adding this Index, maybe it is useful
for other queries too. i think it does not hurt adding an
index on Job because this table never grows like File.
best regards
ulrich
FROM Log INNER JOIN Job USING (JobId) JOIN Pool USING (PoolId)
" . ($arg->{jclient_groups}?
" JOIN Client USING (ClientId)
JOIN client_group_member ON (Client.ClientId =
client_group_member.clientid)
JOIN client_group USING (client_group_id)
WHERE client_group_name IN ($arg->{jclient_groups})
AND
":'WHERE') .
"
Job.StartTime > $arg->{qiso_begin}
AND Job.StartTime < $arg->{qiso_end}
AND ( $filter )
AND Job.Type = 'B'
$filter1
ORDER BY " . ($arg->{qbypool}?"Pool.Name,":""). "Job.JobId,Log.LogId,Log.Time";
--
Ulrich Leodolter <[email protected]>
OBVSG
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
