Effect of payload size on filling the database space

[Former Member]

Hi Experts ,

I am facing an issue in production server that my database size is getting filled when certain interface file comes . I am finding that the file size is very small but the number is high ,will it put a good effect on PI server ( with related to space ) if the file size increases and no. of file decreases ? At present file size is 1.5 MB and it has 40 transaction I can say source team to send 80 transaction in one file and file size will be 3 MB . In that way no. of file will be halved performance wise it will not put any adverse effect as PI best performance is in between 1 to 5 MB(according to sizing document available on SDN) however will it help me in space related issue or not I am not sure ? Kindly advice me for this issue .

Regards,

Saurabh

[baskar_gopalakrishnan2]

PI optimum message size for the performance is upto 5 MB.

Actually the file size is very important factor over here. Decreasing the file number and increasing the file size will not help you for database storage space. Still you get the same problem only. Again I would not go for increasing the file size. Keep the file size smaller as is. You can do message packaging files of smaller size and increase the performance too. PI 7.1 supports message packaging.

Better talk to BASIS team to increase the storage space for database. Also older messages can be archived and move it to backup. This will give enough space backup again for the new messages.

hope that helps

[Former Member]

Thanks Gopal for ur reply . Increasing the storage space of database is already be worked upon . I thought in a simple way that if instead of 3 file we will get only one file having payload less than 5 mb then it will save extra space being used for there pipeline steps . However was not confidant that's why raised this question in forum .At present we are archiving all the file in 3 days to save our database space from filling quickly however was wondering if the no of file will reduce then it will help or not .

Regards,

Saurabh

[former_member181962]

Hi Saurabh,

I think the problem might be due to trace level.

You can check and decrese (or disable trace).

sxmb_adm>integration engine configuration> change global data--> set TRACE_LEVEL to 0.

Best Regards,

Ravikanth Talagana

[maciej_jarecki]

Hi

With DB schema do you mean java or abap db is filled quicklly ? I'm asking because you will need to use other administration tasks for both

BR

Maciej

[Former Member]

Hi Maciej ,

Abap stack where Integration server data is stored . Its getting filed when multiple( thousands of) files are coming but all having small size either 1 Mb or less than it .

@Ravi : Making tracing level 0 or making logging =0 in SXMB_ADM might be help ful but then in sxmb_moni I will neither able to check my payload nor able to see if any error occurs .

Regards,

Saurabh

[maciej_jarecki]

Hi

if you set logging to 0 than you will not see messages processed sucesfully but you will

receive information about error. What kind or archiving and deleting strategy do you use, what are your retention periods ? I my opinion this is place where you should looking for improvments.

Br

Maciej

[former_member181962]

Hi Saurabh,

It is generally a best practice to have trace off in production environments.

Best Regards,

Ravikanth Talagana

[Former Member]

Thanks Ravi I will check with tracing and logging equal to zero actually I have to frequently download the Pi output message so don't want to make logging as zero .Thnaks for ur advice but my original question is still unanswered, is that decreasing the no. of messages put any good effect on Pi server ?

Regards,

Saurabh

[former_member181962]

Hi Saurabh,

I do not think so. reducing/increasing the file size/number of files would affect only runtime performance .

Best Regards,

Ravikanth talagana

[Former Member]

Hi Ravi ,

before closing this thread can we summarize what I should do to reduce the disk space in PI 7.0 Sp18.Kindly add /rectify if needed.

1 .Increase the disk space ( being actioned )

2. Archive the files ( archiving after every three day)

3. trace level and logging should be zero ( wil do it )

4.Reduce the no of file by clubbing the file which are smaller ( less than 1 MB)in size the beauty of this point is I don't have to do any thing for this source team will increase the number of transaction the the gray side is it will not put any effect .

@All :Please update if any more steps can be taken to save the disk space(integration server) from getting filled quickly .

[maciej_jarecki]

Hi

Decrease archiving period to one day for disk space and decrease other parameter for DB space.

BR

MAciej

[Former Member]

Guys any opinion ?? or provide me any related information .

Regards,

Saurabh