🚀 go-pugleaf

In article <umisef.40.30AE344D@halls1.cc.monash.edu.au>,
umisef@halls1.cc.monash.edu.au (Bernd MEYER - Bernie) writes:

> Let me join David in wondering why the number of messages is so small.
> I just did a small test on my linux-laptop. I started two processes that
> were alternately writing into and reading from a named pipe (as in:

This is not the kind of messaging Be times. Messages are addressed packets
of structured data. You create a message, you add typed, named, parameters
(data) to it, you send the message to one of many receivers, the receipient
receives and decodes the message.

There are lower-level primitives in the Be OS, including raw shared memory
plus semaphores, and "ports" which work a lot like message queues. Using
ports, in the simplest fashion, I get 5000 query/reply pairs per second.
This is real-time seconds; I don't know if anything else is happening on
the machine as well (though I doubt it)

I haven't tried shared memory+semaphore, or BMessage (which is probably
what's being quoted) or the direct-to-thread messaging mechanism.

Cheers,

				/ h+




Jon Watte                        Working for Metrowerks, Speaking for myself
h+@metrowerks.com, hplus@bga.com
"I am their leader. I am elected by the people. So I must follow them."