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

Simon Willnauer commented on LUCENE-2787:
-----------------------------------------

after all i think we should really do it. I can not think of any situation 
where you want atime to be updated here. It seems that lots of distributions 
use relatime which is smarter about it see: http://lwn.net/Articles/244829/

we should really document that on the wiki so that folks can check what their 
dist does or by default set it to noatime.

simon

> disable atime for DirectIOLinuxDirectory
> ----------------------------------------
>
>                 Key: LUCENE-2787
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2787
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/*
>            Reporter: Robert Muir
>             Fix For: 3.1, 4.0
>
>         Attachments: LUCENE-2787.patch
>
>
> In Linux's open():
> O_NOATIME
>     (Since Linux 2.6.8) Do not update the file last access time (st_atime in 
> the inode) when the file is read(2). This flag is intended for use by 
> indexing or backup programs, where its use can significantly reduce the 
> amount of disk activity. This flag may not be effective on all filesystems. 
> One example is NFS, where the server maintains the access time.
> So we should do this in our linux-specific DirectIOLinuxDirectory.
> Separately (offtopic), it would be better if this was a LinuxDirectory that 
> only uses O_DIRECT when it should :)
> It would be nice to think about an optional modules/native for common 
> platforms similar to what tomcat provides
> Its easier to test directories like this now (-Dtests.directory)...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to