Wait for all ThreadPool workers to complete

[Michael D. Ober]

I have an application that needs to limit the number of simultaneous threads
that are executing at any given time. The threadpool appears to be ideal
for this. However, I need to have my Sub Main wait until all queued workers
are complete. Is there anyway to do this short of polling a counter?

Thanks,
Mike Ober.

[Michael D. Ober]

Sounds like time to write my own thread/connection pool for the server. The
problem is that too many processor intensive threads on the server and it
bogs down.

Thanks,
Mike.

"Vadym Stetsyak" <va*****@ukr.netwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...

Hello, Michael!

MDOI have an application that needs to limit the number of simultaneous
MDOthreads that are executing at any given time. The threadpool appears
MDOto be ideal for this. However, I need to have my Sub Main wait until
MDOall queued workers are complete. Is there anyway to do this short of
MDOpolling a counter?

AFAIK there is no built-in mechanism in ThreadPool class.
However, you can introduce an array of events that will be set in the
worker threads, while main thread will wait for them.

pseudo code can look like this

//global events list
List<AutoResetEventevents = new List<AutoResetEvent>();

void ThreadWorker()
{
AutoResetEvent finishEvent = new AutoResetEvent(false);

//do some job here

//notify waiting thread
finishEvent.Set();
}

void ThreadThatIsWaitingForWorkers()
{

AutoResetEvent[] waitEvents = events.ToArray();

//wait for all workers to finish
WaitHandle.WaitAll(waitEvents);

}

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Vadym Stetsyak]

Hello, Michael!

You can limit ThreadPool worker thread count.
Or if your server uses sockets you can use async io, like
BeginXXX/EndXXX

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[sloan]

If youre using 2.0 you can limit the total used threads on the ThreadPool.

1.1... there isn't something built in.

I've scoured the internet looking for something like that.

Maybe look at this:
http://dotnetjunkies.com/Tutorial/D7...26FB35F51.dcik
"Vadym Stetsyak" <va*****@ukr.netwrote in message
news:Ou**************@TK2MSFTNGP02.phx.gbl...

Hello, Michael!

You can limit ThreadPool worker thread count.
Or if your server uses sockets you can use async io, like
BeginXXX/EndXXX

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Michael D. Ober]

My server is written in VMS Basic, which requires a separate process for
each connection. It's those processes I have to manage from the client
side.

Mike.

"sloan" <sl***@ipass.netwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...

>
If youre using 2.0 you can limit the total used threads on the ThreadPool.

1.1... there isn't something built in.

I've scoured the internet looking for something like that.

Maybe look at this:
http://dotnetjunkies.com/Tutorial/D7...26FB35F51.dcik
"Vadym Stetsyak" <va*****@ukr.netwrote in message
news:Ou**************@TK2MSFTNGP02.phx.gbl...

>Hello, Michael!

You can limit ThreadPool worker thread count.
Or if your server uses sockets you can use async io, like
BeginXXX/EndXXX

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Greg Young]

and I thought thread per process was unscalable :D
"Michael D. Ober" <obermd.@.alum.mit.edu.nospamwrote in message
news:uh**************@TK2MSFTNGP06.phx.gbl...

My server is written in VMS Basic, which requires a separate process for
each connection. It's those processes I have to manage from the client
side.

Mike.

"sloan" <sl***@ipass.netwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...

>>
If youre using 2.0 you can limit the total used threads on the
ThreadPool.

1.1... there isn't something built in.

I've scoured the internet looking for something like that.

Maybe look at this:
http://dotnetjunkies.com/Tutorial/D7...26FB35F51.dcik
"Vadym Stetsyak" <va*****@ukr.netwrote in message
news:Ou**************@TK2MSFTNGP02.phx.gbl...

>>Hello, Michael!

You can limit ThreadPool worker thread count.
Or if your server uses sockets you can use async io, like
BeginXXX/EndXXX

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Michael D. Ober]

It appears to scale just fine on VMS.

Mike Ober.

"Greg Young" <dr*******************@hotmail.comwrote in message
news:u9**************@TK2MSFTNGP03.phx.gbl...

and I thought thread per process was unscalable :D
"Michael D. Ober" <obermd.@.alum.mit.edu.nospamwrote in message
news:uh**************@TK2MSFTNGP06.phx.gbl...

>My server is written in VMS Basic, which requires a separate process for
each connection. It's those processes I have to manage from the client
side.

Mike.

"sloan" <sl***@ipass.netwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...

>>>
If youre using 2.0 you can limit the total used threads on the
ThreadPool.

1.1... there isn't something built in.

I've scoured the internet looking for something like that.

Maybe look at this:
http://dotnetjunkies.com/Tutorial/D7...26FB35F51.dcik
"Vadym Stetsyak" <va*****@ukr.netwrote in message
news:Ou**************@TK2MSFTNGP02.phx.gbl...
Hello, Michael!

You can limit ThreadPool worker thread count.
Or if your server uses sockets you can use async io, like
BeginXXX/EndXXX

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com