Hi,
We are evaluating OpenSAF as an open-source middleware solution. Our
target environment is a single-node embedded system for now and may be extended
to a cluster later. Performance and memory footprint of OpenSAF services,
especially messages, notification and event distribution, are important for us.
Can somebody shed light on high-level understanding of the communication
mechanism in these services? More specifically,
1. Are OpenSAF daemons (such as osafmsgd and osafmsgnd) involved in every
message passing from a sender to receivers? Or the daemons only act as "name
servers" when setting up the connections between senders and receivers.
2. It seems that OpenSAF allows both sender and receiver to be in the same
process while using these services. If so, is the communication still carried
by TCP/TIPC? Are there any ways to bypass TCP or TIPC, eg., using shared
memory, or passing pointers, to improve the performance for communications
within the same process?
3. Once I start OpenSAF, there are 22 daemons running. Which of them are
mandatory and which are optional? How can I disable these optional
components/daemons to reduce the memory footprint?
4. Are there any benchmark data on any reference/real systems? Is the
overhead of OpenSAF services a real/valid concern for a single-node environment?
Thanks a lot!
Feng
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
