Uploading large documents (50MB or higher) to the Content
Engine from a FileNet® P8
client can cause out-of-memory errors. The following suggestions can
help your site avoid problems with large documents.
If this is an infrequent occurrence
If your
site rarely handles large size documents, try one of these solutions:
- Retry the upload during non-peak usage hours, when there is less
traffic on the network and less use of the specific application server.
- If your site is configured to use WebDav, try adding the document
with WebDav instead of using Workplace XT.
Long term performance tuning
A general guideline
is to allocate at least 4x the document size for the heap setting,
but an even larger amount can be required due to the normal FileNet P8 client user loads
on the system. Here are two methods for estimating the heap space
required by the web server software and the FileNet P8 client:
Method 1: Allow
normal usage on the system for a while, and then let it idle. For
example, run a normal day. Let the system clean up occur overnight
as usual, and then measure usage before the load increases in the
morning.
Method 2: Check the heap size just after a Java™ Garbage Collection, if you can force this
on the web server software being used.
Note: There is a maximum heap
size limit for 32-bit systems of 2GB per process, but the actual heap
size is about 1.6 GB plus other VM or web server process overhead,
which can approach 2GB. This is a limitation of 32-bit Windows operating systems.
- If the heap size is causing the system to swap pages to disk,
reduce the heap size.
- If the Java Garbage Collection
is taking longer than about 3 seconds, reduce the heap size.
For additional heap size recommendations for specific
web servers, see the IBM® FileNet P8 Performance Tuning
Guide.