Subj : Re: Dual core and Multithreading
To   : comp.programming.threads
From : donotcareaboutspam
Date : Tue Sep 27 2005 03:02 pm

Thanks for the replies.

I'm asking because I've developed a library capable of running in the
same process it is linked to, but is also capable of running in an out
of process mode. In that out of process mode it instantiates a dcom
server, logs in to it and then offers the same functionality to the
library user as in the inprocess mode, in which dcom is completely
ignored.

This was made because the app using the library has a heavy cpu load by
itself, so that the second heavy load thread residing in the library
could get offloaded, even onto a separate machine, if required.

So that dcom server acts as a wrapper for the processing thread, and
it's usage was justified because another machine could do the
processing of the library, freeing up cpu resources for the main
application.

But due to stability issues I'm dropping the networked feature, so that
I've come down to ask myself if running the library out of proccess on
the same machine with a dual core or smp adds any advantage over
running that library thread in the same process of the main
application. This way I could drop DCOM/COM completely.

So, do you think that an out of process feature is not needed?

That library basically attaches a thread which does heavy audio
processing and offers an interface to control some parameters of audio
generation.

So, is it the same to use this libray in the same process or is there
any advantage to let it work inside an own process which offers a dcom
interface to the main app?

The point is that I once had an smp machine running win2k, and it would
never spread the workload of a process onto both cpu's, is it possible
that this was only because it could have been a single threaded app
which would have spreaded it it was multithreaded?

Thanks in advance.

.