logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remko Popma <remko.po...@gmail.com>
Subject Re: Running disruptor async performance tests
Date Sat, 29 Mar 2014 07:46:05 GMT
Hi Becky,

The performance test code is a bit messy. Apologies for that.

To answer your questions: I used the longer message for throughput tests,
and the shorter message for latency tests.
PerfTest parameters:
[0] = runner class (like org.apache.logging.log4j.core.
[1] = (blah) is the test name (like "Loggers all async") printed to the
console when a test is started.
[2] = file name to write results to
[3] = thread count (default=3)
followed by optional parameters -verbose and -throughput.

The current implementation of PerfTest runs one throughput and one latency
test, regardless of whether -throughput is specified.

The PerfTestDriver class is the start point for all tests. It sets up
various things like classpath, and system properties to control various
things for different tests. If you use the PerfTest class directly you need
to set up these parameters manually:

The  perf3PlainNoLoc.xml config determines the log file.
The PerfTestDriver would automatically delete this file after each run, you
probably want to do this manually.

Hope this helps,

On Sat, Mar 29, 2014 at 12:03 PM, Rebecca Ahlvarsson

> I am trying to run the async performance tests described on the link below
> on my machine.
> http://logging.apache.org/log4j/2.x/manual/async.html#Asynchronous_Logging_Performance
> I am not an expert with log4j, so here is how far I got after building
> log4j with maven:
> java -cp
> target/classes:target/test-classes:lib/disruptor-3.2.1.jar:../log4j-api/target/classes
> org.apache.logging.log4j.core.async.perftest.PerfTest
> org.apache.logging.log4j.core.async.perftest.RunLog4j2 blah blah.log 1
> -verbose
> Then I get this in the output:
> avg=17 99%=32 99.99%=64 sampleCount=5000000
> 9962247 operations/second
> The questions I have are:
> 1. It looks like the source code IPerfTestRunner uses a much shorter
> message "Short Msg" instead of the 500 characters message stated in the
> link above. Is that intentional or is it a bug? Do we want to test the
> latency with the 500-character message or just a short message?
> 2. I notice that my logs are NOT going to any file. I am probably
> misconfiguring something with log4j. How do I generate a file with the
> messages from the performance test?
> 3. I just want to test with one asynchronous logging thread, so I am
> passing threadCount 1 above. What does the second parameter 'blah' mean?
> 4. Not sure why I get operations/seconds if I am not passing -throughput in
> the command-line. I just want to get the latency numbers for now. After
> that I will worry about throughput.
> So basically I just want to run the same test you run to see those great
> numbers on my production machine.
> Thanks for the help!
> -Becky

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message