[
https://issues.apache.org/jira/browse/PHOENIX-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated PHOENIX-2703:
------------------------------------
Attachment: pe_results.zip
If you're curious, I did a bake off between HBase PE and Phoenix PE
(randomWrite, randomRead, randomSeekScan) with HBase 0.98.17 + Phoenix 4.6.0
and HBase 1.2.0 + Phoenix 4.7.0 (RC2 I think). Flame graphs generated from the
PE runs attached as a zip archive. You might find them interesting. Java
version was 8u60. FAST_DIFF block encoding. Native Hadoop libraries installed
and working. Short circuit reads enabled. I used Java flight recorder to
collect events during the runs with "-XX:+UnlockCommercialFeatures
-XX:+FlightRecorder -XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints"
and then post-processed the results using
https://github.com/chrishantha/jfr-flame-graph . For these tests I also
installed the HBase AccessController as, in part, I was after what its baseline
overhead looks like.
> Port HBase's PerformanceEvaluation to Phoenix
> ---------------------------------------------
>
> Key: PHOENIX-2703
> URL: https://issues.apache.org/jira/browse/PHOENIX-2703
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Attachments: PHOENIX-2703.patch, pe_results.zip
>
>
> I know Phoenix has the very capable Pherf tool but I wanted a test tool as
> similar as possible to HBase's PerformanceEvaluation when making comparisons
> between HBase-only and HBase+Phoenix clusters and clients. Therefore I took
> HBase's PerformanceEvaluation, and replaced HBase API calls with JDBC
> equivalents without touching code where not necessary. The result is a small
> and independent test tool, useful even though we have Pherf. I have the write
> tests and some of the read tests working and tested. I'll post a patch when
> all read tests have been tested, and when I've had a chance to test
> everything using a MR framework.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)