Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Patch Available
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Once you remove almost all performance issues and unnecessary garbage generation, logging starts to sit at the top of method and gc perf profiling (well, xml config still competes on gc - you can improve that 90% and it's still fights to be king of the hill) during test runs. This is the case even with fairly reduced logging and configuration optimizations.

      At that point, exception logging is the big killer (no garbage free option), so in a mostly clean running system this will likely be less the case.

      There are a variety of configuration options that can boost the logging impact. Fairly critical to it all is telling log4j2 that no, Solr is not a webapp, please dont punish.

       

      Attachments

        Activity

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

          People

            Unassigned Unassigned
            markrmiller Mark Robert Miller

            Dates

              Created:
              Updated:

              Time Tracking

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

                Slack

                  Issue deployment