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

Dawid Weiss commented on LUCENE-6002:
-------------------------------------

{code}
Monster("takes ~20GB-30GB of space and 10 minutes, and more heap space 
sometimes")
{code}

all these estimates are *really* hardware-dependent and may be off by an order 
of magnitude I think (just as you can see in the diff). I think SSD vs. regular 
spindle may be one factor, default JVM heap another one.... you can multiply.

This data is valuable, it's just without a context it's no reference for 
anybody -- you should at least include the machine specs from which these were 
measured.
 

> Fix monster tests so they pass
> ------------------------------
>
>                 Key: LUCENE-6002
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6002
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: general/test
>    Affects Versions: 5.0
>         Environment: Linux sauron 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 
> 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.7.0_67"
> Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
> AMD Phenom(tm) II X3 705e, 2.5Ghz
> 12GB RAM
>            Reporter: Shawn Heisey
>            Assignee: Shawn Heisey
>             Fix For: 5.0, Trunk
>
>         Attachments: LUCENE-6002.patch
>
>
> The tests labelled @Monster are having a very hard time passing.  Initially, 
> there were some real failures on tests that push the 2 billion envelope, as 
> well as some test bugs regarding suite timeouts and the quantity of date sent 
> to sysout.  [~mikemccand] committed a fix for the real failures and the 
> initial sysout problems.
> Trying to move @SuppressSysoutChecks to the definition of @Monster didn't 
> work.  I'm also having trouble defining the suite timeouts.  One test that 
> says it takes about 45 minutes hit the six hour timeout that I had configured 
> for the suite, and failed.
> What sort of machine should we use as a "normal" machine for deciding on 
> suite timeouts?  My machine is over four years old, but it's got three 2.5Ghz 
> cores and 12GB of RAM.  That's certainly not a completely modern machine, but 
> it's not exactly slow.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to