changes.
| |  | \\ |
| | \\ |
| | | \\ |
| | An Adobe PDF file consists of numerous compressed object streams. As a PDF file is opened and additional pages are viewed, more objects streams are decompressed, and the memory required to display the content grows significantly. |
 | | \\ |
| | When memory gets low, the ICEpdf Memory Manager frees up memory by disposing the PDF objects associated with previously viewed pages until the required amount of memory is recovered. |
| | \\ |
| | \\ |
| | \\ |
| | {color:#b90000}*Note:*{color} Memory is considered low if the Runtime maxMemory value, minus the current amount of used |
| | Java heap, is less than the specified *org.icepdf.core.minMemory* value. |
| | \\ |
| | \\ |
| | When an image stream is encountered, it is first represented as a byte stream and then encoded into |
| | a viewable image. This process can be time consuming and memory intensive. The image is stored in memory until the Memory Manager disposes of its parent page resources, at which time the encoded image is written to disk and the representation of the image in memory is flushed. The cached image |
| | is from then on read from disk, which may be more efficient than re-decoding the byte stream and re- |
| | encoding the image. |
| | \\ |
| | In some environments, file caching may not be desirable. If necessary, you can turn off caching completely by setting the system property *org.icepdf.core.imagecache.enabled* to false. However, you should not disable file caching if your PDF documents contain large images or several images unless you have a large Java Heap available (512 MB or more). |
| | \\ |
| | For more information on the ICEpdf system properties, see {color:#004ca5}*System*{color} {color:#004ca5}*Properties{*}{color}, p. 10. |
| | \\ |
| | \\ |
| | \\ |
| | | |
| | When the amount of free Java heap memory becomes low, the ICEpdf Memory Manager frees up memory by disposing the PDF objects associated with previously viewed pages until the required amount of memory is recovered. |
| | |
| | {info:title=Note} |
| | Memory is considered low if the Runtime maxMemory value, minus the current amount of used Java heap, is less than the specified *{{org.icepdf.core.minMemory}}* value. |
| | {info} |
| | |
| | When an image stream is encountered, it is first represented as a byte stream and then encoded into a viewable image. This process can be time consuming and memory intensive. The image is stored in memory until the Memory Manager disposes of its parent page resources, at which time the encoded image is written to disk and the representation of the image in memory is flushed. The cached image |
| | is from then on read from disk, which may be more efficient than re-decoding the byte stream and re-encoding the image. |
| | |
| | {info:title=Note} |
| | In some environments, file caching may not be desirable. If necessary, you can turn off caching completely by setting the system property *{{org.icepdf.core.imagecache.enabled}}* to false. However, you should not disable file caching if your PDF documents contain large images or several images unless you have a large Java Heap available (512 MB or more). |
| | {info} |
| | |
| | For more information on the ICEpdf system properties, see {color:#004ca5}*[System Properties]*{color}. |
| | \\ |
| | \\ |
Memory Management and Caching