I have just started to realize the devistating effect that TKLBAM can have on the performance of a Micro instance. It seems that, realistically, anyone wanting to have both uniform website performance and an hourly backup of their server must either move to a Small instance or use some sort of CPU limiter to reduce or eliminate the CPU spiking responsible for AWS CPU throttling.
I would like to experiment with setting up the CPULIMIT utility to accomplish practical throttling for the TKLBAM job, and invite anyone interesed in participating with the experiment by giving me feedback on how to do it. Maybe by the end of the experiment, we may have a bit of an instuction manual on how to practically set it up so TKL enthusasts can keep their micro instances as long as possible before needing to upgrade. Hopefully the last post in this thread can be a comprehensive CPULIMIT AND TKLBAM HOW TO.
To start, I think I can work on setting CPULIMIT up, but I have no idea what names of the process are that I would need to limit. Anyone know;
a) what processes TKLBAM itself uses?
b) is it possible to limit the MYSQLDUMP for the database portion? Would this be counterproductive because it would simply delay table unlocking?
c) Anyone know what part of TKLBAM is most CPU intensive? Is it the rsync or whatever it is that does the comparison to build the incementals that takes the most power? Or is it simply the TKLBAM compression that is the biggest consumer?
I'm starting off in the dark with my understanding of the true nature of TKLBAM, so any tips would be helpful.