🚀 go-pugleaf

umisef@halls1.cc.monash.edu.au (Bernd MEYER - Bernie) writes:

>In article <ACD5092596684DB87@jake-6f.ip.realtime.net> hplus@bga.com (Jon Watte) writes:
>>From: hplus@bga.com (Jon Watte)
>>Subject: Re: Message passing speed on BeBox
>>Date: Sun, 19 Nov 1995 16:17:41 -0600


>>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)

>As I mentioned in my previous post, using the Byte Benchmarks and the
>new scheduler for linux, you can get more than 30000 cycles on a fast
>machine, sending around a single "long" through a pipe.  

Just for comparison, on a SparcStation 10/51, sending a file of size
4194304 as 4-byte messages across a TCP/IP socket (two processes, one
system) took 1.5 seconds. This included dumping the output to /dev/null.
This ain't a terribly scientific measurement, but 700,000 longs/sec is
about what I'd expect from a real system that has 350+ processes running
(though a low load average).

I should expect the BeBox to exhibit at least 4MB/s interprocess communication
bandwidth, since dual 603s are definitely faster than a 50MHz Sparc. If I get
around to it, I'll write an IPC program-pair to test out SysV IPC on the Sparc.
I would expect nearly the same results, if not better, since IPC won't be going
through all the layers of TCP/IP.

Fest3er
-- 
The Microsoft thirty bladed swiss army knife with corkscrew and magnifying lens
[is] inappropriate for all of my word processing needs.

  - Stephanie Evans