AWARE [SYSTEMS]
AWare Systems, Home TIFF and LibTiff Mail List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
January 2016

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
Archive maintained by AWare Systems



New Datamatrix section



Valid HTML 4.01!



Thread

2016.01.25 18:25 "[Tiff] OpenMP enabled libtiff", by Aaron Boxer
[...]
2016.01.29 13:28 "Re: [Tiff] OpenMP enabled libtiff", by Aaron Boxer
2016.01.29 14:46 "Re: [Tiff] OpenMP enabled libtiff", by Bob Friesenhahn
2016.01.29 15:48 "Re: [Tiff] OpenMP enabled libtiff", by Aaron Boxer
[...]

2016.01.29 14:46 "Re: [Tiff] OpenMP enabled libtiff", by Bob Friesenhahn

Thanks. This is exactly the work flow I am interested in: tens of thousands of ~10 MB TIFFs, accessed sequentially. 4 files would be open at a given time. So, even though the files get closed, are you   Only suggesting I will see swapping in this case?

It would not be true swapping or paging-out (actually, there could be some paging out to swap), but there will be memory pressure since memory mapping behaves as a cache. The file data is still in memory (by default) after the file has been unmapped and memory pages are re-claimed (existing contents forgotten, and page re-purposed) for new activity based on new memory pressures, and the time the memory has remained inactive.

The actual behavior is highly OS implementation dependent.

On Unix type systems, the madvise() function can be used to help control behavior of memory-mapped data (e.g. MADV_DONTNEED), but again behavior is highly OS implementation dependent and the only way to know for sure is to test.

Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/