[
https://issues.apache.org/jira/browse/HIVE-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043273#comment-14043273
]
Lefty Leverenz commented on HIVE-7271:
--------------------------------------
[~hagleitn], the wiki has a section for test parameters (hive.test.mode, etc.)
so this can be documented with them. I recommend that the release note &
description explicitly advise people not to set this parameter to true except
when running unit tests. Of course the wiki will link to this Jira so they'll
be able to find the information, but why make them hunt for it?
When HIVE-6037 gets committed, all parameter descriptions will be in
HiveConf.java and then hive-default.xml.template will be generated from
HiveConf.java. You can have an empty description if you prefer, but the
parameter will still appear in hive-default.xml.template at that point.
* [Configuration Properties -- Test Properties |
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-TestProperties]
> 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
> Labels: TODOC14
> 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.2#6252)
