Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2010-11-20 23:35:57 →
Size: 1838
Editor: was
Comment:
← Revision 4 as of 2010-11-20 23:37:36 → ⇥
Size: 2094
Editor: was
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 * We are not going to shoot too high with this project. In particular, our goals do not include adding new authentication systems. We just want to solve exactly one problem: make the notebook scalable. This is of course by far the biggest bug with the Sage notebook, and it is only an issue because the notebook is used so heavily.  * We are not going to shoot too high with this project. In particular, our goals do *not* include adding new authentication systems or making it easy to organize worksheets into folders, etc. We just want to solve exactly one problem: make the notebook scalable. This is of course by far the biggest bug with the Sage notebook, and it is only an issue because the notebook is used so heavily.   That said, it will be useful to think through how to implement everything on the wishlist before deciding on how to implement scalability, so it is easier to implement the other features later.

Preamble

The notebook was written with the intent of being a local GUI, and as a side-effect of taking advantage of the browser, it's usable over the net. But the performance of sagenb.org is terrible since there are around 40,000 users, so we need to make the server much more scalable and robust overall. The plan is currently to tackle this during Sage Days 27.

Tasks

  1. Write testing code to identify bottlenecks, and generally improve robustness.
  2. Convert notebook data structures to a database architecture to allow for concurrent scalable access to a centralized data store by different processes.

  3. Rewrite twist.py to use http://flask.pocoo.org/ flask. The notebook will then depend on Flask and no longer use Twisted. The main advantage to using flask is the excellent support for mod_wsgi.

  4. Use mod_wsgi and Apache (say) to make the server scale massively.

Notes

  • It is OK if the "highly scalable notebook server" has dependencies that the usual single (or small group) server doesn't have. E.g., depending on Apache and a database (like MongoDB) would be just fine, even though neither will be included in Sage.
  • It is, of course, important that the notebook still have a zero configuration mode, where it works fine for a small number of users, but without any complicated dependencies.
  • We are not going to shoot too high with this project. In particular, our goals do *not* include adding new authentication systems or making it easy to organize worksheets into folders, etc. We just want to solve exactly one problem: make the notebook scalable. This is of course by far the biggest bug with the Sage notebook, and it is only an issue because the notebook is used so heavily. That said, it will be useful to think through how to implement everything on the wishlist before deciding on how to implement scalability, so it is easier to implement the other features later.

People

  • Tom Boothby
  • Mike Hansen
  • Alex Leone
  • William Stein