Re: Performance issue

On 1/24/25 13:22, Bill Arlofski via Bacula-users wrote:
> On 1/24/25 10:17 AM, Phil Stracchino wrote:
>>
>> Just FYI I am very unconvinced of the benefit of attribute spooling, at
>> least with a MySQL back-end, because the spooling implementation in
>> Bacula's MySQL driver is very bad.
>>
>>
>> (It writes attributes into a table to avoid writing them into a table,
>> then to unspool, it reads them all out of that table and writes them
>> into the table it otherwise would have written them to in the first
>> place.  Um ......   yeah.  Quite aside from the obvious performance
>> implications,
>
> Hello Phil,
>
> I will let a developer comment on this as it is "Above my pay grade"™, 
> but I can say that I have seen horrific backup performance with 
> attribute spooling disabled. It has been very many years since I last 
> even tried, but apparently it is not (was not?) very efficient to 
> write the attributes of each file to the catalog in real time as the 
> backup is running.
>
>
>> this huge atomic write *also* makes it incompatible with Galera 3 
>> clusters.)

Are you sure about that? The only thing attribute spooling is doing is 
delaying execution of the SQL statements generated by the job. Why would 
Galera care when the SQL was executed?


>
> This is interesting and useful news to me because we have prospects 
> recently coming to us asking about Galera clusters. Thank you. :)
>
>
> Best regards,
> Bill
>
>
>
> _______________________________________________
> Bacula-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-users



_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users