Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #3527] use transactions for large object dumps #1198
This issue has been migrated from Redmine: https://dev.icinga.com/issues/3527
Created by mfriedrich on 2013-01-10 19:16:18 +00:00
this is handy when the config dump on reload/restart happens, not issueing a commit after every single query, but once the data packet is being done processing. e.g. within such a chunk, you'll get server+contacts+contactgroups+etc...
this is experimental, and disabled by default, set use_transactions=1 in ido2db.cfg in order to enable that.
2013-01-10 19:13:46 +00:00 by (unknown) 59776d2
2013-01-10 19:22:08 +00:00 by (unknown) 954349c
Updated by mfriedrich on 2013-01-12 16:40:18 +00:00
A normal startup with my 4k test service setup on a 4core 2gb box with debian 6 and un-tuned mysql 5.1.66
using the git branch with use_transactions=1 in ido2db.cfg
not that much, but still, one gotta optimize mysql and such too, especially when having large scale setups. furthermore, my test config does not have that much dependencies or groups which may slow down the config dump massively.