[omniORB] Optimizing call signature + performance

[Martin B.]

On 06.12.2010 16:44, Thomas Lockhart wrote:
>   > Notes: Typical sequence sizes range from ~10 ... ~hundreds, so each
>>  call transfers very approximately say 100 bytes - 10 kbytes
>>  One specific question that bothers me is whether it could make sense
>>  to block several samples into one call, that is to change the sig
>>  to: ...
>
> That is almost certainly what you will have to do. I think you will find
> the limiting factor is the number of TCP/IP calls per second, not the
> size of the data packet (at least on modern machinery). I haven't look
> at this for some time, but I have found in the past that 5-10k call per
> second was the best you could do (and I may be fudging and scaling that
> up a bit; I'm recalling 1-3k calls per second about 10 years ago).
>

Thanks!


> I would suggest running some TCP/IP packet transfer tests, leaving out
> CORBA, so you get a sense for the performance of your system. Then when
> things are that slow with omniORB, you won't be blaming CORBA for your
> performance limits ;)
>

How large would I make these packets to transfer? When working on a 
TCP/IP socket I'm (logically) just "streaming" data, or don't I? I 
vaguely remember there being a maximum message size (maybe the term is a 
bit different) for TCP/IP messages on Windows as well as some omniORB 
setting relating to a max msg size ... ??

cheers,
Martin