[
https://issues.apache.org/jira/browse/PHOENIX-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391069#comment-14391069
]
James Taylor commented on PHOENIX-1287:
---------------------------------------
This is good work, [~shuxi0ng]. Try your performance test with a VARCHAR column
that's not in the primary key constraint, as you might see different
performance characteristics (as columns in the primary key constraint end up in
the row key while other columns end up as KeyValues). I believe you can add a
column to the CREATE TABLE call in performance.py. [~mujtabachohan] - any
difficulty in doing that, and will the column automatically be populated? What
controls the values with which it'll be populated?
[~shuxi0ng] - another option is to use our new Pherf tool -
http://phoenix.apache.org/pherf.html, as this kind of performance comparison is
exactly what it was designed for.
Please let me know if the pull request is up-to-date and I'll give it a review.
Thanks so much for the excellent contributions.
> Use the joni byte[] regex engine in place of j.u.regex
> ------------------------------------------------------
>
> Key: PHOENIX-1287
> URL: https://issues.apache.org/jira/browse/PHOENIX-1287
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Shuxiong Ye
> Labels: gsoc2015
>
> See HBASE-11907. We'd get a 2x perf benefit plus it's driven off of byte[]
> instead of strings.Thanks for the pointer, [~apurtell].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
