You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/24 21:49:40 UTC

[jira] [Updated] (PHOENIX-1689) Instrument thread pool used by Phoenix to help judge pool size and queue depth

     [ https://issues.apache.org/jira/browse/PHOENIX-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-1689:
----------------------------------
    Assignee:     (was: Samarth Jain)

> Instrument thread pool used by Phoenix to help judge pool size and queue depth
> ------------------------------------------------------------------------------
>
>                 Key: PHOENIX-1689
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1689
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Samarth Jain
>
> To get a better idea of what should be the right thread pool size and the associated queue depth, it is necessary that we instrument the thread pool used by phoenix for servicing requests. An initial list of the metrics that we can capture contains:
> 1) Time spent by tasks to be picked up by a thread in the pool. 
> 2) Overall time spent by tasks in the pool - from submission to completion
> 3) Service time - time it took to execute the task
> 4) Number of requests being submitted to the pool. 
> It would also be nice to make the choice of using an instrumented thread pool vs a regular one configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)