Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-5557

Core threading redesign

    XMLWordPrintable

Details

    • Task
    • Resolution: Obsolete
    • Critical
    • 12.1.13.Final
    • 7.2.2.Final
    • Core
    • None

    Description

      Infinispan needs a lot of threads, because everything is synchronous: locking, remote command invocations, cache writers. This causes various issues, from general context switching overhead to the thread pools getting full and causing deadlocks.

      We should redesign the core so that most blocking happens on the application threads, and the number of internal threads is kept to a minimum.

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. ISPN-5467 Design new interceptor interfaces for sequential invocation

          • 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.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. ISPN-5468 Change the interceptors to move the new sequential interfaces

          • 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.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. ISPN-5469 Remote-executor threads should not block during RPCs

          • 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.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. ISPN-5470 Remote-executor threads should not block to acquire locks

          • 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.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. ISPN-6610 Interceptors should avoid forkInvocationSync

          • 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.
          • Closed
          is related to

          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) ISPN-4847 Improve indexing performance

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              wburns@redhat.com Will Burns
              dberinde@redhat.com Dan Berindei (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: