You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2015/04/18 19:44:58 UTC

[jira] [Updated] (LUCENE-6436) add LuceneTestCase.SuppressFsync

     [ https://issues.apache.org/jira/browse/LUCENE-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir updated LUCENE-6436:
--------------------------------
    Attachment: LUCENE-6436.patch

Patch. Omitting fsyncs is not intrusive so I also change the rate from 90% to 99%.

> add LuceneTestCase.SuppressFsync
> --------------------------------
>
>                 Key: LUCENE-6436
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6436
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>         Attachments: LUCENE-6436.patch
>
>
> Filesystem chain is a per-class decision. Either fsyncs are passed thru to the hardware or not globally for the test. If you have a really slow test, this can cause occasional unbearably slow runs when it gets unlucky.
> {code}
>   /**
>    * Annotation for test classes that should avoid always omit
>    * actual fsync calls from reaching the filesystem.
>    * <p>
>    * This can be useful, e.g. if they make many lucene commits.
>    */
>   @Documented
>   @Inherited
>   @Retention(RetentionPolicy.RUNTIME)
>   @Target(ElementType.TYPE)
>   public @interface SuppressFsync {
>     String[] value();
>   }
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org