[ 
https://issues.apache.org/jira/browse/HIVE-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071081#comment-17071081
 ] 

Peter Vary edited comment on HIVE-23103 at 3/30/20, 3:47 PM:
-------------------------------------------------------------

Merged patch with HIVE-23076
{code}
With patch:
Operation                      Mean     Med      Min      Max      Err%    
openTxn0-1                     12.72    12.17    10.78    24.23    16.37   

With only  HIVE-23076:
Operation                      Mean     Med      Min      Max      Err%    
openTxn0-1                     15.87    14.07    12.21    80.44    48.32 
{code}


was (Author: pvary):
Merged patch with HIVE-23076

With patch:
Operation                      Mean     Med      Min      Max      Err%    
openTxn0-1                     12.72    12.17    10.78    24.23    16.37   

With only  HIVE-23076:
Operation                      Mean     Med      Min      Max      Err%    
openTxn0-1                     15.87    14.07    12.21    80.44    48.32 

> 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.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)

Reply via email to