sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaomeng Huang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-508) Improve runtime of 'Sentry Hive Tests' (currently it is >30m)
Date Wed, 19 Nov 2014 07:10:33 GMT

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

Xiaomeng Huang commented on SENTRY-508:
---------------------------------------

Hi, [~lskuff] 
I think this can be an umbrella jira, now I have two improvement to cut down the Hive-e2e-tests(47
min to 42 in my local). If it make sense to you, I will create two sub-task to attach the
patch.

> Improve runtime of 'Sentry Hive Tests' (currently it is >30m)
> -------------------------------------------------------------
>
>                 Key: SENTRY-508
>                 URL: https://issues.apache.org/jira/browse/SENTRY-508
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Lenni Kuff
>             Fix For: 1.5.0
>
>
> Below is a breakdown of the execution time for each for each Sentry package. In most
cases, the test runtime is low but the Sentry Hive Tests take 33 minutes to complete. We should
revisit this test suite to see if the runtime can be cut down.
> {code}
> Sentry	19 sec
> Sentry Bindings	  0.11 sec
> Sentry Binding for Hive	42 sec
> Sentry Binding for Solr	6.1 sec
> Sentry core	0.1 sec
> Sentry Core Common	17 sec
> Sentry Core Model DB	3.2 sec
> Sentry Core Model Solr	6.1 sec
> Sentry Distribution	33 sec
> Sentry Policies	 2.9 sec
> Sentry Policy Common	0.63 sec
> Sentry Policy for Databases	26 sec
> Sentry Policy for Search	17 sec
> Sentry Providers	87 ms
> Sentry Provider Cache	6 sec
> Sentry Provider Common	17 sec
> Sentry Provider DB	3 min 33 sec
> Sentry Provider File	11 sec
> Sentry Tests	95 ms
> Sentry Hive Tests	33 min
> Sentry Solr Tests	3 min 30 sec
> {code}



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

Mime
View raw message