How to avoid ebonding performance issues when large attachments are considered?

[Suggy]

We are doing ebonding between 2 ServiceNow instances.

When sending attachment from instance A to B, where the file size is 100 mb, it took almost 20 seconds.

If I send a small file (say 1mb), its reflecting within 2s.

Question - Is there any issue/limitations for large files? Anything happening behind the scenes while large files are consdiered?

We need to send/reflect the attachments immediately, not 20s or so.

Is it possible?

[Suggy]

Anyone has any feedback or comments?

[Suggy]

Anyone?

[Sohail Khilji]

Hi @Suggy ,

your question was missed !

Question - Is it fine to send large attachments? Any performance issues to the instance? If yes, how to avoid when dealing with large files?

The answer is Yes, if its done safely with all preventive measures you can avoid performance issues. 

Firstly you need to figure out the scope and see why such large attachements are needed, see you can zip the file to reduce the size and the load this will reduce the size drastically.

See if you can sync the attachements durning non business hours if possible.

20s must be fine it is not a synchronous process. The problem with larget attachements is that they hold more space in you DB and do not look tidy. it becomes hard to manage them later when they db size peaks.

Do some offline work to see if you can reduce the size of file before it reaches servicenow instance.

[Suggy]

HI @Sohail Khilji  as I have mentioned, its a eboding project. So the data should reflect real time 🙂

As end users attach the file, we cannot zip it. Also the system propert OOB allows 1024 mb. But we have changed it to 100 mb.