Re: Thread Pool Performance in real-time applications

From:

Ulrich Eckhardt <eckhardt@satorlaser.com>

Newsgroups:

microsoft.public.vc.language

Date:

Thu, 22 Apr 2010 09:14:17 +0200

Message-ID:

<9j95a7-6nu.ln1@satorlaser.homedns.org>

Jack wrote:

As my game application require more than 12 mobile units to do
pathfinding at the same time, I wonder if I implement a thread
pool (and that means to use a task queue for awaiting tasks) for
those objects, would that really affect the overall performance
of the application?

If you have more than one core, using multiple threads can give you a
performance gain. However, if the threads each lock a mutex on a shared map
where they search their path, you obviously don't get anything. Also, if
the operations are partially IO-bound and partially CPU-bound, you would
already get an advantage for a single CPU.

General suggestion: Use one more thread than you have CPUs.

Concerning your question about a thread pool, don't bother now. If you start
implementing the task queue, you can easily change the implementation from
synchronous execution to using a thread pool without affecting the overall
design.

Uli

--
C++ FAQ: http://parashift.com/c++-faq-lite

Sator Laser GmbH
Gesch??ftsf??hrer: Thorsten F??cking, Amtsgericht Hamburg HR B62 932