Benjamin W Herta/Fishkill/IBM@IBMUS wrote on 02/27/2012 11:49:23 AM:
>
> As for the extra threads, I tried running our NQueensDist sample program
> with X10_STATIC_THREADS=true and X10_NTHREADS=1, and I see that we get
> three threads, when we should be getting one. The extra threads appear
to
> be coming from our garbage collector. We'll look into this further.
>
Thanks Ben. I forgot about those.
We configure the GC by default to do parallel marking. I believe this
causes it to create 1 GC worker thread per CPU (up to a max of 16). This
can be disabled by editing x10.runtime/build.xml and removing the argument
--enable-parallel-mark in the calls to configure in the build-bdwgc target
and then doing a distclean; dist to rebuild everything. These threads
should only be active during a GC (when no other X10 threads are running
because we are using stop-the-world GC).
If we're running multiple places per machine, then the GC threads may end
up oversubscribing the machine, since each of them will create GC threads
at a level to fully exploit the available CPUs during the mark phase of the
GC.
--dave
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
X10-users mailing list
X10-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/x10-users
