[
https://issues.apache.org/jira/browse/PHOENIX-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002534#comment-14002534
]
Mujtaba Chohan commented on PHOENIX-35:
---------------------------------------
Tested Phoenix 3.0 current head (hash cbbb26451eed723b5f0fd51a8e9170b19d7017ad)
with HBase 0.94.18. Memory usage on client is now significantly less than last
test and remains within 1GB using Phoenix upsert batch size of 15K. Unsalted
table used for test consists of 60 bytes PK and 14 integer columns in unique
CFs. Single Mutable index is created on 3 integer columns during data load.
Following table shows client memory and CPU usage.
!mem-usage.png!
Previous results are available [here|
https://github.com/forcedotcom/phoenix/issues/412]
> Perf test memory usage for indexes
> ----------------------------------
>
> Key: PHOENIX-35
> URL: https://issues.apache.org/jira/browse/PHOENIX-35
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: James Taylor
> Assignee: Mujtaba Chohan
> Fix For: 3.0.0
>
> Attachments: mem-usage.png
>
>
> [~jesse_yates] fixed this [1] issue, so in theory our memory usage should be
> much better now. Requires HBase 0.94.14 or newer.
> [1] https://github.com/forcedotcom/phoenix/issues/412
--
This message was sent by Atlassian JIRA
(v6.2#6252)