[
https://issues.apache.org/jira/browse/HIVE-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040246#comment-14040246
]
Gunther Hagleitner commented on HIVE-7271:
------------------------------------------
I removed the asserts because it turns out that they are firing all the time in
our unit tests. However since we execute the queries in a separate jvm that
doesn't have assertions turned on they are ignored. Finally - even when they
fire they result in correct query execution. Seems they were useful some time
ago, but don't have any meaning anymore.
In other words: In today's hive, "assert XXX" will only fire if you write an
actual unit test (not .q files). We should probably switch to throwing
assertion error or use guava's preconditions to encode certain conditions in
hive.
[~brocknoland]/[~szehon] it might be possible to run with less than 8GB. I
added that to run hashtable gen in process with all the other stuff. What
instance type are we using currently?
> 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)
