Re: multi-threading

[Charles Wilt <charles.wilt@xxxxxxxxx>]

The thing to consider is that threading originally came out as a
"light weight" process.

On the i as well as other platforms, it is expensive to create a
process (aka JOB).  The real problem other platforms have is that
given the VM design, it is also expensive to switch between processes.
 Whereas on the i, given its single level store, switching between
processes takes basically a single (GOTO) instruction; on other
platforms it can take upwards of 1000 instructions to switch between
processes.

Thus, threading gave the ability to do mutliple tasks at the same time
without having to start multiple processes.

HTH,
Charles


On Fri, Sep 4, 2009 at 4:12 PM, Chris Bipes<chris.bipes@xxxxxxxxxxxxxxx> wrote:
> I decided to start a new thread for the question, why?  In all my
> business programming I have never needed to write a multithreaded
> application.  I have worked with a system that has multiple
> communication jobs that dump request into queues, then have multiple
> server programs that process the queued entries and issue responses.
> But never needed on job to handle multiple threads.
>
>
>
> So I ask all of you for an application that requires multiple threads in
> a single process.  Any real world examples out there?
>
> Chris Bipes
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.