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

ASF GitHub Bot commented on IGNITE-8251:
----------------------------------------

GitHub user udaykale opened a pull request:

    https://github.com/apache/ignite/pull/4577

    IGNITE-8251 Reduce testPageEviction run time

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/udaykale/ignite IGNITE-8251

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4577.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4577
    
----
commit 8d3021205018312347cc171b960481eca3fab1ed
Author: uday <udaygkale@...>
Date:   2018-08-20T06:58:01Z

    IGNITE-8251 Reduce testPageEviction run time

----


> Reduce testPageEviction run time
> --------------------------------
>
>                 Key: IGNITE-8251
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8251
>             Project: Ignite
>          Issue Type: Test
>          Components: persistence
>            Reporter: Dmitriy Pavlov
>            Assignee: Uday Kale
>            Priority: Minor
>              Labels: newbie
>
> Cache 3 and suite IgniteBinaryObjectsCacheTestSuite3 several times executes 
> one test testPageEviction  and each run requires significiant time.
> RandomLruNearEnabledPageEvictionMultinodeTest.testPageEviction duration 6m 
> 9.41s 
>  Random2LruNearEnabledPageEvictionMultinodeTest.testPageEviction duration 5m 
> 51.353s 
>  RandomLruPageEvictionMultinodeTest.testPageEviction duration 5m 36.529s 
> It is necessary to understand what exactly the test does and shorten the 
> execution time by 
> - reducing the number of objects 
> - the region size 
> - the desired run time. 
> Or some other parameter which help to run this test faster.
> At the same time, it is necessary to leave the test coverage unchanged.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to