[Insight-developers] Multi-threading strategies

[Blezek, Daniel J (GE, Research)]

Hi all,

  I was debugging a multi-threaded registration metric today, and gdb
nicely prints thread creation/destruction messages.  In our current
MultiThreader, pthreads are created/joined in the scatter/gather
pattern.  For a general filter, this isn't likely to be a problem,
'cause it executes only once (in general).  For optimization metrics, it
may be called thousands of times, leading to a huge number of pthreads
created/joined.  Is this efficient?  Would it be worth while to
investigate keeping threads around, rather than joining them?  They
could simply sit idle until they have something to do...  This would
reduce overhead, but may add complexity, but we only need to get it
right once...

  Stephen Aylward: any comments?

-dan

Daniel Blezek, PhD
GE Global Research
Computer Scientist

T 518 387 5481
F 518 387 6981
D *833-5481
E blezek at research.ge.com
www.research.ge.com

1 Research Circle
Niskayuna, NY 12309, USA

General Electric Company

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.itk.org/mailman/private/insight-developers/attachments/20070727/28f8cae5/attachment.htm