Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-2391

Investigate ThrowableProxy performance

Agile BoardAttach filesAttach ScreenshotAdd voteVotersStop watchingWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.11.1
    • None
    • None
    • None

    Description

      I've noticed when applications get into a state where they log more exceptions than usual (e.g. network connectivity issues) thread dumps contain many threads working inside of ThrowableProxy, loading classes.

      A simple jmh benchmark of a pattern layout writing to disk with a message and throwable appears to write about 160,000 events/second using a throwable, and 2,000 events/second using ThrowableProxy.
      I will investigate to understand where the substantial difference is coming from, and clean up the benchmarks to add to the log4j2 benchmarking module.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ckozak Carter Kozak
            ckozak Carter Kozak

            Dates

              Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 20m
              20m

              Slack

                Issue deployment