Boost Log运行时优化

Dim*_*los 8 c++ logging boost boost-log

我正在为我的应用程序的日志记录平台使用Boost-Log和全局严重性记录器.分析表明,boost::log::v2s_mt_posix::core::open_record最多可占用总执行时间的25%.

我确实有很多日志消息,但我不希望它们如此昂贵,因为它们的严重性较低,而且它们被过滤掉了.

有没有办法让这些消息在运行时不那么昂贵?(再次:我希望即使在过滤时也会有一个小的开销,当然,当没有过滤时,它会更大).

通过创建一些包装器宏,编译时相对容易"修复".

更新样本工作代码:

#include <cmath>
#include <iostream>
#include <string>
#include <boost/lexical_cast.hpp>
#include <boost/log/sources/global_logger_storage.hpp>
#include <boost/log/sources/severity_logger.hpp>
#include <boost/log/trivial.hpp>
#include <boost/log/sources/severity_channel_logger.hpp>
#include <boost/log/common.hpp>
#include <boost/log/expressions.hpp>
#include <boost/log/sinks.hpp>
#include <boost/log/utility/setup/common_attributes.hpp>
#include <boost/log/utility/setup/console.hpp>
#include <boost/log/support/date_time.hpp>
#include <boost/utility/empty_deleter.hpp>
#include <boost/shared_ptr.hpp>
#include <boost/make_shared.hpp>

// severity levels
enum severity_level {INFO};

// Logging macro
#define LOG(level) BOOST_LOG_SEV(global_logger::get(), level)

// Initializing global boost::log logger
typedef boost::log::sources::severity_channel_logger_mt<
    severity_level, std::string> global_logger_type;

BOOST_LOG_INLINE_GLOBAL_LOGGER_INIT(global_logger, global_logger_type)
{
    return global_logger_type(boost::log::keywords::channel = "global_logger");
}

// Initialize terminal logger
void init_logger(int verbosity)
{
    namespace bl = boost::log;
    typedef bl::sinks::synchronous_sink<bl::sinks::text_ostream_backend>
      text_sink;

    boost::shared_ptr<text_sink> sink = boost::make_shared<text_sink>();
    sink->locked_backend()->add_stream(
        boost::shared_ptr<std::ostream>(&std::cout, boost::empty_deleter()));

    sink->locked_backend()->auto_flush(true);

    sink->set_formatter(bl::expressions::stream << bl::expressions::message);

    sink->set_filter(bl::expressions::attr<severity_level>("Severity")
                     < (severity_level) verbosity);

    bl::core::get()->add_sink(sink);
    bl::add_common_attributes();
}

int main(int argc, char* argv[])
{
    init_logger(boost::lexical_cast<int>(argv[1]));
    for(int i = 0; i < 200; ++i)
    {
        std::sin(std::sin(17.2)); // dummy processing
        LOG(INFO) << "A message!";
    }
    return 0;
}
Run Code Online (Sandbox Code Playgroud)

使用参数运行0不会打印任何日志消息,但它需要两倍(!)的时间而不是注释掉LOG消息.

小智 0

通常,在记录日志时,必须评估正在记录的内容,并且该评估发生在实际决定是否记录之前。例如:

log.debug("The current state of the system is: " + system.expensiveFunctionToGatherState());
Run Code Online (Sandbox Code Playgroud)

我们有一个自行开发的日志系统,它将当前时间添加到日志中,这是对gettimeofday(). 结果发现,程序中 20% 的 CPU 消耗是调用了gettimeofday()从未到达任何地方的日志函数。