Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-8995

Orient's OLogManager spends lot of CPU time to do nothing

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Database
    • Labels:
      None

      Description

      Was running nexus-perf + yourkit combo, and something striking caught my eye:

      According to Yourkit, ~10% of cpu time spent by system was doing this:

      java.util.logging.Logger.getLogger(String)
      

      By closer inspection, it seems that Orient's OLogManager does this. Interestingly, it also implements "levels", and it does have debug=true by default. This means, that all the debug logs went thru completely, only to be discarded by JUL (or SLF4J?).

      It seems OLogManager should be synced with log levels, as if debug would be set to false, it would prevent using 10% of CPU time to get the loggers from JUL.

      Either NX log manager should be made aware of Orient OLogManager to set it's levels properly, or some other means would be needed to keep the two in sync.

      Notes:

      • I saw this class pop up in Yourkit "hot spots" with 8-9% of CPU time
      • interestingly, it could not regularly reproduce this, so this one might be a "red herring", act only if we see it again?

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            cstamas Tamás Cservenák
            Last Updated By:
            Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title