[
https://issues.apache.org/jira/browse/HIVE-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084813#comment-17084813
]
Peter Vary commented on HIVE-23103:
-----------------------------------
With the new changes batching will not be relevant for openTxns, but become
relevant for commitTxn.
Attaching the new patch, and the microbench results:
{code}
Baseline:
Benchmark (dbProduct) (txnType) Mode Cnt Score
Error Units
TxnHandlerBenchRunner.commitTxn ORACLE DEFAULT ss 100 42.988 ±
4.569 ms/op
TxnHandlerBenchRunner.commitTxn ORACLE READ_ONLY ss 100 45.029 ±
4.686 ms/op
After patch:
Benchmark (dbProduct) (txnType) Mode Cnt Score
Error Units
TxnHandlerBenchRunner.commitTxn ORACLE DEFAULT ss 100 36.208 ±
3.869 ms/op
TxnHandlerBenchRunner.commitTxn ORACLE READ_ONLY ss 100 37.038 ±
3.746 ms/op
{code}
> Oracle statement batching
> -------------------------
>
> Key: HIVE-23103
> URL: https://issues.apache.org/jira/browse/HIVE-23103
> Project: Hive
> Issue Type: Improvement
> Components: Transactions
> Reporter: Peter Vary
> Assignee: Peter Vary
> Priority: Major
> Attachments: HIVE-23103.02.patch, HIVE-23103.patch
>
>
> Examine how to really get better performance for oracle statement batches.
> [Oracle JDBC
> doc|https://docs.oracle.com/cd/E11882_01/java.112/e16548/oraperf.htm#JJDBC28752]
> describes:
> {quote}The Oracle implementation of standard update batching does not
> implement true batching for generic statements and callable statements. Even
> though Oracle JDBC supports the use of standard batching for {{Statement}}
> and {{CallableStatement}} objects, you are unlikely to see performance
> improvement.
> {quote}
> I would look for connection properties to set, so it is handled anyway, or if
> not, then use:
> {code}
> begin
> query1;
> query2;
> query3;
> end;
> {code}
> to we will have only a single roundtrip for the db.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
