[omniORB] What is the effect of changing the max message size on general memory consumption

[Sylvain Joyeux]

How would changing the max message size affect general memory
consumption ? Is there some preallocation happening, or will it have an
effect only on the ORBs that actually send/receive big messages ?

I've googled it a bit, but could only find a single message without
answers ...
--
Sylvain Joyeux (Dr.Ing.)
Senior Researcher

Space & Security Robotics
Underwater Robotics

!!! Achtung, neue Telefonnummer!!!

Standort Bremen:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Stra?e 5
28359 Bremen, Germany

Phone: [phone]
Fax: [phone]
E-Mail: robotik at dfki.de

Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Stra?e 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973
Steuernummer: 19/673/0060/3
-----------------------------------------------------------------------

[Duncan Grisby]

Post by Sylvain Joyeux
How would changing the max message size affect general memory
consumption ? Is there some preallocation happening, or will it have an
effect only on the ORBs that actually send/receive big messages ?

There's no pre-allocation linked to the maximum message size. As long as
there aren't actually any big messages, there's no harm to having a
really huge limit. Even with big messages, omniORB tries to minimise
buffering, so you don't generally use lots of memory within omniORB
itself, just within whatever application-level data structures there
are.

The limit is there to protect from buggy or malicious senders that send
data claiming to be enormous. It's easy to send a GIOP message that
claims to be 2GB in size, or that contains a sequence with billions of
entries, for example. A na?ve receiver of such a message could allocate
a buffer to hold the contents, even if there actually isn't that much
data available.


Cheers,

Duncan.