> Yeah, but usually they should only happen if high reliability is asked > for. In the "normal" settings, they happen very infrequently. Thus I > would be really interested to learn the source of the CPU utilization. > David, have you experienced something like this?
I have probably found a main culprit for CPU load iff the .qi file is synced very often: there is a sprintf() used to generate the filename, and it is done each time the file is opened. I think this stemmed back to the time when this function was only called at rsyslog termination. I am moving this out to queue construction (it actually is a constant string!). That should already relieve some of the CPU load. Still, this doesn't happen in default settings, so > @Brian: could you try to reproduce this in a lab and help gather some > info on what's going on? (I will also see if I can reproduce it here). That would still be quite useful ;) Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
