[ 
https://issues.apache.org/jira/browse/HIVE-23819?focusedWorklogId=456269&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-456269
 ]

ASF GitHub Bot logged work on HIVE-23819:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Jul/20 17:53
            Start Date: 08/Jul/20 17:53
    Worklog Time Spent: 10m 
      Work Description: pvary commented on pull request #1230:
URL: https://github.com/apache/hive/pull/1230#issuecomment-655666860


   Can we have microbenchmarks for serializing/deserializing for edge cases at 
least?
   * Everything is one big range
   * Everything is single event
   * Everything is 2 long range
   
   Thanks,
   Peter


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 456269)
    Time Spent: 20m  (was: 10m)

> Use ranges in ValidReadTxnList serialization
> --------------------------------------------
>
>                 Key: HIVE-23819
>                 URL: https://issues.apache.org/jira/browse/HIVE-23819
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Peter Varga
>            Assignee: Peter Varga
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Time to time we see a case, when the open / aborted transaction count is high 
> and often the aborted transactions come in continues ranges.
> When the transaction count goes high the serialization / deserialization to 
> hive.txn.valid.txns conf gets slower and produces a large config value.
> Using ranges in the string representation can mitigate the issue somewhat.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to