For interactive provider on Redhat Linux 6/7 upa8.0.0.L1.linux.rrg, is there a limit to the confi...

For interactive provider on Redhat Linux 6/7 upa8.0.0.L1.linux.rrg, is there a limit to the configuration parameter, maxfragmentsize? In our config value is 64K (65536). However, on connection ADH, we the value down-graded to default.

Find more posts tagged with

elektron

elektron-sdk

elektron-transport-api

eta-api

rrt

interactive-provider

Accepted answers

Jirapongse

@Kam.Anjorin

First of all, I would like to explain more about maxFragmentSize in UPA.

maxFragmentSize defines the maximum size buffer that will be written to the network. If a larger buffer is required, the RSSL Transport will internally fragment the larger buffer into smaller maxFragmentSize buffers. This is different from application-level message fragmentation done via the Message Package. Moreover, any guaranteed, shared, or input buffers created will use this size.

Setting this value to this high value means you can send a large buffer without fragmentation at transport level. However, the application will reserve a lot of memory for guaranteed, shared, or input and output buffers.

The default value of maxFramentSize is 6144 bytes and the maximum size is 65535 bytes.

Please explain more why you need to set this value to 65535 and what the size of each message is sent by the application.

All comments

Kam.Anjorin

We could not successfully use the higher config value 65536. We had to use 32K. Please inform if this is an internal TREP limitation. On the positive, when the maxFragmentSize is higher we observed that we could transmit large buffers and increase our throughput.