[gclist] Fibers v.s. Threads

Greg Colvin gcolvin@us.oracle.com
Thu, 29 Jun 2000 11:52:19 -0600

From: Charles Fiterman <cef@geodesic.com>
> At 11:33 AM 6/29/00 -0600, you wrote:
> >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.
> That is try to be a process. Its really very good advice. Most threads
> users have no business using threads.

That's one reason for the advice.  The other reason is that Oracle is
already a multi-threaded server, and they are better off leveraging
off that than trying to write their own.