atari83 opened a new issue, #332: URL: https://github.com/apache/logging-log4cxx/issues/332
Hello! So, I'm working on a program that produce about 100K rows of data per minute and approximately each row is about 2K. While using simple and straightforward `FileAppender` works just fine. I was thinking how could I optimize it more. Please help me to see if I understand it correctly: 1- Using AsyncAppender would potentially assist me to solve the write-operations blocking issues. 2- It is possible to configure the BufferSize (bounded-buffer) parameter in XML DOM. But then I dont know what is default value, or how should I calculate it based on my program context. 3- The FileAppender also exposes BufferedIO and BufferSize. Again, I dont know what is default behavior and If I need to use that or not (the calculation method..) 4- Based on the nature of AsyncAppender class (asynchronous-based operations), there could be a situation that some data get aborted when application exited. If thats correct, Is there anyway that let me enforce the AsyncAppender object to write down remaining data before program exited ? My last question is not related to Appenders, but I just wanted to know if it is possible to call the `DOMConfigurator::configure` function multiple times in my program ? I'm asking this, because lets say I'm using logging different logs for different log-levels. So, based on the configured value for <priority> in <category> tags, I would actually let the program to generate the logs I'd expected to see. For now, every time I want to change the log-level I have to restart the program. I was thinking if it applicable to call the function to reload the xml file to change the log-level for example and without requiring program to get restart ? Thanks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
