Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 23 Jun 2014 03:59:24 +0000 (UTC)
From: "Brock Noland (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12722995.1403414539182.26646.1403495964657@arcas>
In-Reply-To: <JIRA.12722995.1403414539182@arcas>
References: <JIRA.12722995.1403414539182@arcas>
Subject: [jira] [Commented] (HIVE-7271) Speed up unit tests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brock Noland commented on HIVE-7271:
------------------------------------

We specify the number of q files to include in a "test batch" and that number is much less than the number of q file tests. Thus we probably aren't seeing as much benefit. After this change we can probably increase the batch size.

> 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
>         Attachments: HIVE-7271.1.patch, HIVE-7271.2.patch, HIVE-7271.3.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.2#6252)