Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>This is not a correctness problem because the actor library will spawn more threads as necessary (is that right?)</p> </blockquote> <p>So far as I understand, that is not right. The actor is blocked, and sending another message to it causes that message to sit in the actors mailbox until that actor can <code>receive</code> it or <code>react</code> to the message.</p> <p>In Programming in Scala (1), it explicitly states that actors should not block. If an actor needs to do something long running it should pass the work to a second actor, so that the main actor can free itself up and go read more messages from its mailbox. Once the worker has completed the work, it can signal that fact back to the main actor, which can finish doing whatever it has to do.</p> <p>Since workers too have mailboxes, you will end up with several workers busily working their way through the work. If you don't have enough CPU to handle that, their queues will just get bigger and bigger. Eventually you can scale out by using remote actors. <a href="http://akka.io" rel="nofollow">Akka</a> might be more useful in such cases. </p> <p>(1) Chapter 32.5 of Programming in Scala (Odersky, Second edition, 2010)</p> <p>EDIT: I found this: </p> <blockquote> <p>The scheduler method of the Actor trait can be overridden to return a ResizableThreadPoolScheduler, which resizes its thread pool to avoid starvation caused by actors that invoke arbitrary blocking methods.</p> </blockquote> <p>Found it at: <a href="http://www.scala-lang.org/api/current/scala/actors/Actor.html" rel="nofollow">http://www.scala-lang.org/api/current/scala/actors/Actor.html</a></p> <p>So, that means depending on the scheduler impl you set, perhaps the pool used to run the actors will be increased. I was wrong when I said you were wrong :-) The rest of the answer still holds true.</p>
    singulars
    1. This table or related slice is empty.
    1. POscala actors vs threads and blocking IO
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAnt Kutschera
    1. USAnt Kutschera
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POscala actors vs threads and blocking IO
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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