[gclist] Fibers v.s. Threads

[Greg Colvin]

From: Boehm, Hans <hans_boehm@hp.com>
> What do typical clients look like?  My impression was that this is an
> unusual JVM, which tends to run large numbers of relatively simple clients
> concurrently?  And the clients are unlikely to run for very long without
> making calls that allow suspension?  If that's the case, I wouldn't expect
> non-preemptive thread scheduling to be an issue.

>From my perspective it is hard to guess at what a typical client
might be, but they are not necessarily simple.  We do encourage
users to structure their code as multiple virtual machines rather
than multiple threads, with shared state in the database.

> Are there clients that are both computationally intensive and drive GUIs in
> concurrent threads?

We don't support any kind of GUI for our VM, which is running
inside our database server, on a machine that may not even have
a console.