On 11/20/10 4:05 PM, Tom Boothby wrote:
On Sat, Nov 20, 2010 at 1:45 PM, William Stein<wst...@gmail.com> wrote:
To solve this slowness problem will require probably at least a month
of focused work to completely reimplement basically from scratch the
storage and server architecture of the notebook in a much more
scalable way. Nobody is working on this, though if nobody else does
it, then I'll do it sometime in the next year. So the options are:
We've got a bug days coming up next year (January), and a man-month
between you, me, Alex Leon, and Mike Hansen (provided they're willing
to play along) -- plus whoever else is willing to join.
Tasks:
(1) Write testing code to identify bottlenecks, and generally
improve robustness.
(2) Convert all notebook data structures to a database architecture.
(3) rewrite twist.py to use flask.
(pre-3): evaluate whether we want to change from twisted to something
else. For example, it seems like flask will not support websockets for
a long time, but Alex has some really cool demos/ideas for applications
of websockets in the notebook.
(4) Use mod_wsgi and apache to make it scale massively.
(4b) package nginx or lighttpd or something with Sage so that Sage still
comes with a webserver?
Thanks,
Jason
--
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
URL: http://www.sagemath.org
