This shows you the differences between two versions of the page.
|
cache [2013/02/25 19:06] LtWorf details on benchmark |
cache [2013/02/25 19:12] (current) LtWorf typo |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| It should be noted that modification time of a directory is updated only when files are created or removed, hence if a file has been modified but already existed, the modification time of the directory will not be updated. | It should be noted that modification time of a directory is updated only when files are created or removed, hence if a file has been modified but already existed, the modification time of the directory will not be updated. | ||
| - | To overcome this problem weborf uses inotify to know when a file is being modified, and invalidate the cache. Since inotify is Linux specific, on other platforms, cache will be invalidated only upon file creation or deletion. | + | To overcome this problem weborf uses inotify to know when a file is being modified, and invalidate the cache. Since inotify is Linux specific, on other platforms cache will be invalidated only upon file creation or deletion. |
| - | The use of inotify can be inhibited by using the --fastcache option, that will allow a faster startup, a smaller memory footprint at the expense of the possibility of having incorrect results. | + | The use of inotify can be inhibited by using the --fastcache option; that will allow a faster startup, a smaller memory footprint at the expense of the possibility of having incorrect results. |
| In some situations it could be perfectly safe to use the --fastcache option, for example if one wants to list .tar.gz files that are just added or removed but never modified themselves. | In some situations it could be perfectly safe to use the --fastcache option, for example if one wants to list .tar.gz files that are just added or removed but never modified themselves. | ||