Alan is right. The problem is not the inserting itself but the fact, 
that Storage is blocked while the job do not need it more. If I disable 
attribute spooling the attributes will be stored with data and the time 
the job spends will be the same (I think).
The database performance is another problem and we do some other steps 
to improve that (we use postgres). I will need to vacuum it often and 
maybe some dump-and-restore will help.


Alan Brown napsal(a):
> On Wed, 7 Oct 2009, Cedric Tefft wrote:
> 
>> The second phase (what you describe as DIA) is a result of using  "Spool
>> Attributes = yes" in your job defs.  Changing this to no MIGHT solve
>> your problem.  OTOH, it might actually make things worse.  I suggest you
>> look up the Spool Attributes directive in the manual.
> 
> If you're spooling data then attributes will spool as well. However I
> believe that Marek is referring to the sometimes LONG delay to release
> FD/SD after attribute despooling has finished that occurs while database
> inserts take place.
> 
> I agree with the OP that once the job has finished the FD and SD should be
> released while database (batch) inserts are done, in order to allow other
> jobs to proceed.
> 
> Marek: make sure you tune your database for performance. The default mysql
> configuration is quite slow and setup for machines with very little
> memory by current standards.
> 
> AB
> 
> 
> 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users