Uploaded image for project: 'OpenJPA'
  1. OpenJPA
  2. OPENJPA-1648

Slice thread pool breaks down under high concurrency

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.1.0
    • slice
    • None

    Description

      Slice thread pool breaks down under heavy usage [1].
      This is due to poor choice of thread pool.

      Also creation of thread pool for every flush() is inefficient.

      Simple solution will be to use a cached thread pool – which will be upper bounded by available system's capacity for concurrent native threads.

      Attachments

        Activity

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

          People

            ppoddar@apache.org Pinaki Poddar
            ppoddar@apache.org Pinaki Poddar
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment