Uploaded image for project: 'XWiki Platform'
  1. XWiki Platform
  2. XWIKI-17334

The notification gathering thread pool configuration is not used anymore

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • 12.4
    • 12.2
    • Notifications
    • Unknown
    • N/A
    • N/A

    Description

      The point of the thread pool (with a size of 2 by default) was to reduce the impact of the (very expensive) notification gathering on the XWiki instance.

      The refactoring done in XWIKI-17052 skipped that to only rely on async rendering. While it does not block http threads (but that's actually not true for notification count) it still produce way too much threads doing notification calculation. For example it makes myxwiki.org barely usable.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. XWIKI-17052 Allow to inject Javascript / CSS in Notification Displayer

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. XWIKI-17338 Handle getting cached async content with JSX with an AJAX request

          • Major - Major loss of function.
          • Closed
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. XWIKI-17336 Allow the async rendering framework to limit the pool of threads based on AsyncRenderer type

          • Major - Major loss of function.
          • Closed

          Activity

            People

              surli Simon Urli
              tmortagne Thomas Mortagne
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: