Re: [scala-user] Profiling Actor-based server: Lots of time in FJTaskRunner
Erik, Alex, John, et al,
i'm loathe to hijack this thread -- which is a good one -- but the experience with the lock up described below is really just the tip of the iceberg. Unless specific scheduling contracts and semantics can be worked out, a pluggable scheduling architecture is just asking for disaster. Worse, it means that a whole host of compiler support that could be provided to apps that use actor-based concurrency is null and void because those solutions (be they model-checking or types-based) will critically depend on specific ranges of scheduling semantics.
Actors and other higher level concurrency constructs are a major appeal of languages like scala. If they prove themselves to be "not ready for prime time" the impact on perception might not be contained to just that usage of the language.
On Mon, Mar 2, 2009 at 11:55 AM, Erik Engbrecht <[hidden email]> wrote:
FYI - My work still uses the same scheduler. I've noticed the FJTaskScheduler2 is sometimes overly aggressive in spawning threads, especially if you have a lot of cores, but last time I poked at that particular piece of code it became too conservative with spawning threads and locked up.