[kepler-dev] Threading in kepler

[Norbert Podhorszki]

Hi Tristan,

AFAIK there is no any director in Ptolemy, that can assign multiple 
threads to an actor. PN executes exactly one thread per actor.

Generally, people would become very angry if an actor would silently 
process tokens in parallel:
a. what if tokens depend on each other?
b. order of tokens can change.

Your nicest solution would be to create a new director which can execute 
an actor in parallel ;-)

Norbert

      Norbert Podhorszki
    ------------------------------------
      University of California, Davis
      Department of Computer Science
      1 Shields Ave, 2236 Kemper Hall
      Davis, CA 95616
      (530) 754-8188
      pnorbert at cs.ucdavis.edu
      ----------------------------------


On Wed, 13 Sep 2006, Tristan King wrote:

> hi guys,
>
> basically i'm looking for a bit of an explaination on how threading
> works in kepler, and any ideas to what i might be able to do to solve
> the below problem.
>
> I'm running into a problem where my kepler workflow isn't able to
> keep up with the data being created from processing (thus my data
> queue is getting full and dying).
>
> My workflow consists of a source which polls a data queue for new
> data and when new data arrives, sends that data (an xml parcel) to
> the rest of the workflow.
>
> Each data processing pipeline in the workflow is independent on the
> progress of the other pipelines, thus new threads could be started to
> preform the processing task.
>
> However, it seems to me that each Actor in the workflow only runs a
> single thread for each actor. (i'm using the PN Director).
>
> Is there a way i can spawn a new thread to preform a particular
> pipeline, while leaing my data source in a single thread producing data?
>
> Thanks for any help you can give me.
> --Tristan
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
>