[
https://issues.apache.org/jira/browse/HIVE-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040263#comment-14040263
]
Gunther Hagleitner commented on HIVE-7271:
------------------------------------------
bq. We shouldn't remove the hadoopShims check of local mode, in MapRedTask
right? Shouldn't user still able to set this via the mr-specific flags?
I think this was done to "fix" something broken in the unit tests. The user can
always choose in or out of process via the hive conf var (submit via child).
This is independent of using local job runner or not (right now we always run
out of process in local mode.)
bq. Not related to this change, but can this method name be refactored as it's
confusing (now its executing in process and not in child jvm)
Yes, this is cheesy. I'll fix that.
> 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
>
>
> 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)
