Re: RMS and threads
From: SteveL (infovax_at_hotmail.com)
Date: 09/22/04
- Next message: James O'Shea: "Sniffer Can't see cluster traffic"
- Previous message: Tom Linden: "Re: OpenVMS Pearl - Indian Railways Celebrates 10th anniversary using HP Technology"
- In reply to: Hein: "Re: RMS and threads"
- Next in thread: Jonathan Cronin: "Re: RMS and threads"
- Reply: Jonathan Cronin: "Re: RMS and threads"
- Reply: Joshua Lehrer: "Re: RMS and threads"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 22 Sep 2004 08:10:41 -0700
Thanks for your reply.
>when you use the master to control, all overlap is gone.
I don't quite see why this is the case. If I have, say, a 4 CPU
system, one master thread and two worker threads then there's no reason
why they can't all execute simultaneously.
For as long as the threads are still busy (writing their little batch
of records - between 1 and 100 on each wakeup), I expect them to
execute concurrently. That's the whole premise for my use of threads
in this application.
I do expect some overhead, of course, but perhaps less than I'm
currently seeing.
>This should be more pronounced when disk IO is involved
Can you elaborate on that for me? Is there something within RMS which
doesn't make full use of a multi-CPU system, or which otherwise
serialises on a per-process rather than a per-thread basis?
I recall from the dim, distant past that some component of RMS (the
XQP?) had a hard-coded affinity for CPU 0, but I thought that had been
lifted.
On my 2 CPU system (an AlphaServer ES47 7/1000), each thread seems to
be idle (waiting on its condition variable) for an average of 0.0005
seconds per "wake-up" when I have the cross-thread synchonisation
enabled.
To my mind, this is pretty quick, although the accumulated time does
make a significant difference to the end result, but others have
suggested that there's a problem to be solved here somewhere.
I guess the real questions are.... 1) is there anything in RMS that is
not entirely thread-efficient, and.... 2) just how fast can kernel
threads be scheduled for execution if they're always going from wait,
to computable, to I/O, and back to wait again?
Any and all ideas, references, etc, much appreciated.
Thanks again,
SteveL.
- Next message: James O'Shea: "Sniffer Can't see cluster traffic"
- Previous message: Tom Linden: "Re: OpenVMS Pearl - Indian Railways Celebrates 10th anniversary using HP Technology"
- In reply to: Hein: "Re: RMS and threads"
- Next in thread: Jonathan Cronin: "Re: RMS and threads"
- Reply: Jonathan Cronin: "Re: RMS and threads"
- Reply: Joshua Lehrer: "Re: RMS and threads"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|