On 07/27/2011 01:18 PM, Jafar Al-Gharaibeh wrote: > > If there were a way to query Unicon for the number of > threads/co-expressions, that might be useful. > I could run that in a separate thread and watch the growth. (The same > thread could monitor string/heap/etc > memory consumption.) > > > Querying the number of live threads is a fine idea, add to that ways to > query specific thread state like how much > memory is used by the thread or how many garbage collection done by the > thread. We thought about extending several > keywords to do such things. We may see such extensions in near future > releases.
Hi Jafar, Thanks for the explanation(s). They all make sense. I'm mildly surprised that allocating a 'new' co-expression's resources is that much more expensive than refreshing an existing set of resources, but I don't know anything about the implementation anymore! I'll try to be patient as things get added in. Thanks again! -- Steve Wampler -- [email protected] The gods that smiled on your birth are now laughing out loud. ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Unicon-group mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unicon-group
