Generic Message Payload Size?

RicknBaker

Right next question. Now I've got a .Net ValueAdd Provider and Consumer exchanging XML data using OMM generic messages. Is there a limit to the payload size? Some of our documents are about 40 Mbyte. Is that too big? Should I consider zipping them up first?

umer.nalla

Hi @RicknBaker

As mentioned above RSSL can handle large payloads.

However, when I was looking at large payloads a while back, I was recommended that in order optimise the data distribution across the TREP infrastructure, I should ideally limit the size to no greater then 6k bytes. This is the size of the RSSL message buffer in the infrastructure. Larger messages mean the infrastructure has to break up and re-assemble at the expense of extra resources.

You mentioned in your other posts that data wont be sent too often, so you may not be overly concerned about performance - but you should discuss with your Market Data team about possible impact on other users of your TREP infrastructure.

Based, on the above, zipping the data would appear to be a good idea - however, you should do some testing to determine for yourself the suitability of doing so.

If you take a look at our tutorial on Decoding Machine Readable News you will note that we zip and split our larger news payloads into smaller fragments for distribution. The consumer then has to unzip and re-assemble the fragments to get the full payload.