You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Shannon Ladymon (JIRA)" <ji...@apache.org> on 2015/08/11 00:38:45 UTC

[jira] [Commented] (HIVE-7271) Speed up unit tests

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

Shannon Ladymon commented on HIVE-7271:
---------------------------------------

The TODOC14 label has been removed from this issue, although the documentation has not been reviewed. [~hagleitn], if you review the documentation in the future and notice anything that needs to be changed, please let Lefty (or myself) know.

> Speed up unit tests
> -------------------
>
>                 Key: HIVE-7271
>                 URL: https://issues.apache.org/jira/browse/HIVE-7271
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Gunther Hagleitner
>            Assignee: Gunther Hagleitner
>             Fix For: 0.14.0
>
>         Attachments: HIVE-7271.1.patch, HIVE-7271.2.patch, HIVE-7271.3.patch, HIVE-7271.4.patch, HIVE-7271.5.patch, HIVE-7271.6.patch, HIVE-7271.7.patch
>
>
> Did some experiments to see if there's a way to speed up unit tests. TestCliDriver seemed to take a lot of time just spinning up/tearing down JVMs. I was also curious to see if running everything on a ram disk would help.
> Results (I ran tests up to authorization_2):
> - Current setup: 40 minutes
> - Single JVM (not using child JVM to run all queries): 8 minutes
> - Single JVM + ram disk: 7 minutes
> So the ram disk didn't help that much. But running tests in single JVM seems worthwhile doing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)