You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Pinaki Poddar (JIRA)" <ji...@apache.org> on 2010/05/05 18:33:05 UTC
[jira] Updated: (OPENJPA-1648) Slice thread pool breaks down under
high concurrency
[ https://issues.apache.org/jira/browse/OPENJPA-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pinaki Poddar updated OPENJPA-1648:
-----------------------------------
Assignee: Pinaki Poddar
> Slice thread pool breaks down under high concurrency
> -----------------------------------------------------
>
> Key: OPENJPA-1648
> URL: https://issues.apache.org/jira/browse/OPENJPA-1648
> Project: OpenJPA
> Issue Type: Bug
> Components: slice
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 2.1.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.