Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3608

There is no way to define core pool size for io subsystem

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 5.0.0.Alpha6
    • 4.0.0.Alpha10
    • IO
    • None

    Description

      There is no way how to define core pool size for underlying thread pool in IO subsystem's worker (/subsystem=io/worker=*). It is only possible to set task-max-threads which defines max pool size for underlying thread pool.
      Suggestion for improvement: Add new attribute to set core pool size to IO subsystem worker

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. WFLY-10056 Subystem changes tracker for new thread pool implementation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          clones

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-8434 There is no way to define core pool size for io subsystem

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          relates to

          Task - Represents a small unit of work that is not end-user facing. WFCORE-3827 Test coverage for thread pool attribute propagation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              tomazcerar Tomaž Cerar (Inactive)
              rjanik@redhat.com Richard Janik
              Jan Kašík Jan Kašík
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: