On Wed, 19 Aug 2009, William Stein wrote: > > On Wed, Aug 19, 2009 at 1:19 AM, Robert > Bradshaw<rober...@math.washington.edu> wrote: >> Multithreading will have to be introduced at one >> level or another to scale the notebook to more than a single >> processor anyways. >> >> - Robert > > Huh? Why? I don't see any need for multithreading to solve the > above problem, or rather I don't understand what problem you're > talking about. The notebook already scales to more than a single > processor.
I am talking about the case where there are enough users that the notebook process itself becomes the bottleneck. It all depends on how lightweight the shuffling data between the underlying processes and the browser is, and how many concurrent users one wants to support for a single notebook. In the asynchronous model there is only one thread handling all of the connections. (Also, anything long-running, e.g. taring up all a users worksheets for download, needs to spawn a separate thread/process.) Of course if the whole setup is running on a single machine, it may be that the computational processes are always the bottleneck. > I also now know precisely what Glenn Tarbox's original problem is, > since I've recently also experimented with using the Interactive > Broker's API from the notebook. It's an interesting nontrivial > problem. I hope to provide some demo code for Glenn once I work this > out... Yes, my comment was completely independant of his original issue. - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
