Why won't DSO multi-thread ???

Hi,

I've written a little app, in C# with the 1.1 .Net Framwork, to process
partitions. It can use multiple threads to connect to the same AS2000
database and process the partitions. The work list is divided up between the
thread instances before they are started, so we know they are not blocking
each other. And any given cube is not processed by more than 1 thread.

When we run with 2 threads, on a 2 CPU machine, our through-put drops by 30%.
If we run 2 instances of the APP, with 1 thread each, our through-put goes
up by 30%.

It seems that clsPartition.Processs method is the sticking point, although
each thread has it's own instance. Is this something to with the properties
of the clsPartition class?

Hi,

Do you set MTA/STA attribute respectively?
Do you open connection with server in the same thread as it used?

IMHO, it is better to use multiple processes to interoperate with COM-world
(DSO) definitively from one thread. (I make so too).

Vladimir

"Al" <Al (AT) discussions (DOT) microsoft.com> schrieb im Newsbeitrag
news:C0A65E28-1151-4163-B10F-996BC47FFD2B (AT) microsoft (DOT) com...

Hi,

I've written a little app, in C# with the 1.1 .Net Framwork, to process
partitions. It can use multiple threads to connect to the same AS2000
database and process the partitions. The work list is divided up between
the
thread instances before they are started, so we know they are not blocking
each other. And any given cube is not processed by more than 1 thread.

When we run with 2 threads, on a 2 CPU machine, our through-put drops by
30%.
If we run 2 instances of the APP, with 1 thread each, our through-put goes
up by 30%.

It seems that clsPartition.Processs method is the sticking point, although
each thread has it's own instance. Is this something to with the
properties
of the clsPartition class?

If you are trying to process multiple partitions or dimensions in parallel
using .net code which calls AS2K DSO, forget it. DSO is COM, and the code
will serialize in the COM calls even if you create multiple threads from your
own .net code. To do it, you need to create a seperate program (or use the
processpartition.exe utility to do the processing) and then create/launch
multiple processes from your .net code in the background. The .net code can
poll those processes and check when they have completed.

Steve Green

"Al" wrote:

Hi,

I've written a little app, in C# with the 1.1 .Net Framwork, to process
partitions. It can use multiple threads to connect to the same AS2000
database and process the partitions. The work list is divided up between the
thread instances before they are started, so we know they are not blocking
each other. And any given cube is not processed by more than 1 thread.

When we run with 2 threads, on a 2 CPU machine, our through-put drops by 30%.
If we run 2 instances of the APP, with 1 thread each, our through-put goes
up by 30%.

It seems that clsPartition.Processs method is the sticking point, although
each thread has it's own instance. Is this something to with the properties
of the clsPartition class?

try the parrallel process utility.


"Al" <Al (AT) discussions (DOT) microsoft.com> wrote

Hi,

I've written a little app, in C# with the 1.1 .Net Framwork, to process
partitions. It can use multiple threads to connect to the same AS2000
database and process the partitions. The work list is divided up between
the
thread instances before they are started, so we know they are not blocking
each other. And any given cube is not processed by more than 1 thread.

When we run with 2 threads, on a 2 CPU machine, our through-put drops by
30%.
If we run 2 instances of the APP, with 1 thread each, our through-put goes
up by 30%.

It seems that clsPartition.Processs method is the sticking point, although
each thread has it's own instance. Is this something to with the
properties
of the clsPartition class?