Databases
StackOverflow2013
Postsdbo
POProcessing concurrently in Scala
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProcessing concurrently in Scala
    primarykey
    data
    text
    <p>As <a href="https://stackoverflow.com/questions/1007010/can-scala-actors-process-multiple-messages-simultaneously/1007310#1007310">in my own answer to my own question</a>, I have the situation whereby I am processing a large number of events which arrive on a queue. Each event is handled in exactly the same manner and each even can be handled independently of all other events. </p> <p>My program takes advantage of the Scala concurrency framework and many of the processes involved are modelled as <code>Actor</code>s. As <code>Actor</code>s process their messages sequentially, they are not well-suited to this particular problem (even though my <em>other</em> actors are performing actions which <em>are</em> sequential). As I want Scala to "control" all thread creation (which I assume is the point of it having a concurrency system in the first place) it seems I have 2 choices:</p> <ol> <li>Send the events to a pool of event processors, which I control</li> <li>get my <code>Actor</code> to process them concurrently by some other mechanism</li> </ol> <p>I would have thought that #1 negates the point of using the actors subsystem: <em>how many processor actors should I create?</em> being one obvious question. These things are supposedly hidden from me and solved by the subsystem.</p> <p>My answer was to do the following:</p> <pre><code>val eventProcessor = actor { loop { react { case MyEvent(x) =&gt; //I want to be able to handle multiple events at the same time //create a new actor to handle it actor { //processing code here process(x) } } } } </code></pre> <p>Is there a better approach? Is this incorrect?</p> <p><em>edit: A possibly better approach is:</em></p> <pre><code>val eventProcessor = actor { loop { react { case MyEvent(x) =&gt; //Pass processing to the underlying ForkJoin framework Scheduler.execute(process(e)) } } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USoxbow_lakes
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POProcessing concurrently in Scala
      1. USoxbow_lakes
      1. VTFavorite
    2. VO
      singulars
      1. POProcessing concurrently in Scala
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POProcessing concurrently in Scala
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAlthough actors dont seem to support a pool of workers directly, this Q was helpful in exposing this deficiency. All the docs available to me, dont mention this explicitly.
      singulars
      1. POProcessing concurrently in Scala
      1. USePharaoh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload