PI QuickSizer Question

[Former Member]

Hi,

I'm filling in the PI 7.3 quicksizer and have a question regarding a file -> XI Proxy scenario.

If the file sent is a large flat file (1 Gb) , and  we follow the guideline in the quicksizer which only considers

the outbound messages. The file adapter lets you specify the number of recordsets per message in the Content Conversion tab , recordset per message field.

If I consider this and make my messages be 10 Mb each the scenario will not be too heavy on the system requirements.

Is this correct... ? What I'm mainly getting at is that the initial file size of 1 Gb is never really considered in the sizer in this scenario. However, wont a huge inbound file have an impact on the memory requirements of the server. Perhaps the file adapter just reads each record sequentially and never loads the whole file in memory.

Thanks.

[former_member184720 · Accepted solution]

Hi Thierry -

Yes.the initial 1 GB size is never considered in this case as the file is being split into 10 different messages in PI.

Also i don't think you'll have memory issues either.

As per the SAP note: 821267 i see that -

14. Memory Requirements

• Q: Which memory requirements does the File Adapter have? Is there a restriction on the maximum file size it can process?
• A: The maximum file size that can be processed by the File Adapter depends on a number of factors:
  • The most important one is the size of the Java heap, which is shared  among all messages processed at a certain point in time. In order to be  able to process larger messages without an out of memory error (OOM), it  is recommended to increase the size of the available Java heap and/or to reduce the concurrency in the system so that fewer messages are processed in parallel.
  • Another factor negatively influencing the maximum message size in  releases up to and including XI 3.0 SP 13 is an enabled charcter set (encoding) conversion if the message type is set to "Text".
  • Using the transport protocol "File Transfer Protocol (FTP)" also uses  more memory for processing than the transport protocol "File System (NFS)" (up to and including XI 3.0 SP 13).
  • If the Message Protocol "File Content Conversion" is used in a File  Sender channel, consider that not only the size of the input file  affects the File Adapter's memory usage, but even more the size of the  XML resulting from the conversion, which is usually a few factors larger than the original plain text file.
    
    To reduce the memory consumption in this scenario, consider configuring  the setting "Maximum Recordsets per Message" for the sender channel.  This will cause the input file to be split into multiple smaller mesages.

Regards,

Hareesh