Phil,
I repeat here my previous email message which refers to your email
below, but I mistakenly attached to your schema email. Sorry for the
repetition.
================
Hello Phil,
Thank you for your comments, and I am pleased that you have found a
solution for your batch insert problem. Unfortunately, I cannot apply
the patch to a released version two days before I go on vacation. Nor
will I change the default.
If you can show me solid statistics on a Linux system that for the most
current MySQL inserting between 20 and 50 million records in a single
job is slower with batch insert than without it, I will ask the authors
of the code to take a look at it or at least explain. Otherwise, I
trust their judgment. That said, it may well be for smaller workloads
and a properly tuned MySQL it could be more efficient to do normal inserts.
Best regards,
Kern
On 08/05/2017 05:48 PM, Phil Stracchino wrote:
Kern,
Regarding the batching for attribute data - based on your explanation of
how it works, I'm at a loss to understand why the person who wrote the
MySQL code thought that was a good idea in the first place. It seems
the only thing it accomplishes is to write all of the attribute data
TWICE. I need to look at the code more, but at this point I'm really
thinking that the entire batching idea was ill-conceived from the start.
It's possible it MIGHT have once been a good idea IF using legacy
MyISAM tables, but honestly, the world would be better off had the
MyISAM storage engine died with MySQL 4.1 in the late 90s.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
