You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:21:40 UTC

[jira] [Resolved] (PHOENIX-359) Bad performance for multi-thread env?

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

Gabriel Reid resolved PHOENIX-359.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> Bad performance for multi-thread env?
> -------------------------------------
>
>                 Key: PHOENIX-359
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-359
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: Raymond Liu
>
> 1.  I observed that within one JVM, if I fork a lot of thread to connect with phoenix via jdbc, the performance is bad, no matter how much thread I open, it doesn't show much difference. CPU is always around 200% ( on top),   since I do have 24 Core there, the overall cpu load is just around 8%
> 2. the phoenix.query.threadPoolSize doesn't helps, I set it from 10 or 240, no obvious difference.
> However, If I run it with multiple JVM, each for 1-2 thread, It do improve CPU usage. So it seems to me there must be something no going well with multiple thread env. might be some lock mechanism? thread waiting on lock for each other ?
> Any Idea on this?



--
This message was sent by Atlassian JIRA
(v6.2#6252)