One small detail to keep in mind at this point: only the "discard" and "overwrite" modes are implemented for handling buffer condition. If you need to ensure that events are _never_ discarded, even with high-throughput scenarios, we might need to implement a "blocking" mode, which makes the application wait until there is space free in the buffer before it continues. It would probably make more sense for logging.
Other than this detail, LTTng-UST would be a good fit for low-overhead logging. Thanks, Mathieu * Alawneh, Luay ([email protected]) wrote: > Hi, > > I am reading about LTTng and I would like to know if it can replace Log4c for > logging user space events in the production environment. In addition to the > method enter/exit events we also use Log4c to log many other events to > indicate errors and other useful information. > > To summarize, I would like to know if LTTng can be used in a production > environment for logging different types of events. We are planning to replace > Log4c with another logging framework to improve the performance by reducing > the time spent in logging. > > Thanks, > > Luay Alawneh > Nuance Communications > > _______________________________________________ > lttng-dev mailing list > [email protected] > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev -- Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
