Re: Logback performance improvements

Just for fun I decided to add some more tests to the file appender benchmark. I’ve checked them in. Please review them to see if everything is configured so the tests make sense. Note that I would expect the async appenders to reduce to the speed of the file appender, since once the queue fill

Re: Logback performance improvements

Whoa, I wonder how async MMF benchmarks compare. Also, I wonder if there's some sort of cloud service out there we can use for free to run benchmarks on a regular basis. Might even be doable with a dedicated VM on builds.apache.org. On 11 February 2017 at 13:37, Apache wrote: > Just for fun I de

Re: Logback performance improvements

I don't think it is a good idea to mix async tests with sync tests. We already have separate benchmarks for the various ways to log asynchronously, if you want to compare them just run those also. JMH makes it super easy to build benchmarks but we have to be very careful that the test really

[jira] [Created] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

Remko Popma created LOG4J2-1811: --- Summary: Log4j 2 configuration/usage ergonomics Key: LOG4J2-1811 URL: https://issues.apache.org/jira/browse/LOG4J2-1811 Project: Log4j 2 Issue Type: Epic

[jira] [Created] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

Remko Popma created LOG4J2-1812: --- Summary: Improve error message when log4j 2 configuration file not found Key: LOG4J2-1812 URL: https://issues.apache.org/jira/browse/LOG4J2-1812 Project: Log4j 2

[jira] [Commented] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

[ https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862651#comment-15862651 ] ASF subversion and git services commented on LOG4J2-1812: - Commit

[jira] [Commented] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

[ https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862652#comment-15862652 ] Remko Popma commented on LOG4J2-1812: - Added above text to the error message in commi

[jira] [Updated] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

[ https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1812: Description: When configuration fails because no Log4j 2 configuration file is found, the followin

[jira] [Commented] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

[ https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862653#comment-15862653 ] ASF subversion and git services commented on LOG4J2-1812: - Commit

[jira] [Commented] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

[ https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862655#comment-15862655 ] Ralph Goers commented on LOG4J2-1811: - I'm all for documentation, but I have to note

[jira] [Created] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

Remko Popma created LOG4J2-1813: --- Summary: Provide shorter and more intuitive way to switch on Log4j internal debug logging Key: LOG4J2-1813 URL: https://issues.apache.org/jira/browse/LOG4J2-1813 Projec

[jira] [Updated] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

[ https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1813: Description: People find it difficult to troubleshoot Log4j 2 configuration issues. Many people do

[jira] [Commented] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

[ https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862663#comment-15862663 ] Remko Popma commented on LOG4J2-1811: - I agree our documentation is very good and cer

[jira] [Comment Edited] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

[ https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862663#comment-15862663 ] Remko Popma edited comment on LOG4J2-1811 at 2/12/17 6:00 AM: -

Build failed in Jenkins: Log4jScala #18

See -- Started by upstream project "Log4j 2.x" build number 2660 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H14 (ubuntu) in workspace

[jira] [Commented] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

[ https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862675#comment-15862675 ] Ralph Goers commented on LOG4J2-1813: - If I am not mistaken, the change Matt just imp

[jira] [Commented] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

[ https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862677#comment-15862677 ] Ralph Goers commented on LOG4J2-1812: - I had always intended to have the capability t

[jira] [Commented] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

[ https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862680#comment-15862680 ] Ralph Goers commented on LOG4J2-1811: - I have my doubts about how possible that is. M

Re: Logback performance improvements

I added the tests so you guys could run them and take a look. I have no problem with the changes being reverted. As I think I said, I expected most of the async appenders to back up. I expected them to be a bit slower, but I didn’t expect them to be as slow as they are when the queue is full. I

Re: Logback performance improvements

The queue is bigger but still fills up quickly because all the benchmarks do is add events as quickly as possible and the FileAppender can't keep up with that rate. Sent from my iPhone > On Feb 12, 2017, at 16:19, Apache wrote: > > I added the tests so you guys could run them and take a look