|
Size: 745
Comment:
|
Size: 3004
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| 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'', so we need to make the server more robust overall. The plan is currently to tackle this during [[days27|Sage Days 27]]. | 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 [[days27|Sage Days 27]]. == Scratch documents == * [[https://docs.google.com/document/d/19R8AEc-l_MytmOduyPpsTxcXk_9cwnStOCrZuFTFgLs/edit?hl=en|Google Docs Scratchpad]] to keep track of tasks == Google Code Repositories == * [[http://code.google.com/r/mhansen-flask/|Mike Hansen's Flask Branch]] * [[http://code.google.com/r/wstein-sd27/source/browse|William Stein's Sage Days 27 Notebook Branch]] |
| Line 8: | Line 19: |
| 1. Convert all notebook data structures to a database architecture. 1. rewrite twist.py to use flask: http://flask.pocoo.org/. 1. Use mod_wsgi and apache to make it scale massively: http://code.google.com/p/modwsgi/. |
1. Convert notebook data structures to a database architecture to allow for concurrent scalable access to a centralized data store by different processes. 1. 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. 1. Use [[http://code.google.com/p/modwsgi/|mod_wsgi]] and Apache (say) to make the server scale massively. == Notes == * Be aware of the [[http://groups.google.com/group/sage-devel/browse_thread/thread/e6eb1d3f8b85b4fd|sage-devel discussion]]. * 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. * A proposal for a scalable server: [[https://docs.google.com/document/d/1uYJXPAWypGgb92QStJ19cW-29y4-hn5hi8oXMR-11TU/edit?hl=en&authkey=CISp9cQB|google docs link]] and [[https://groups.google.com/d/msg/sage-notebook/3jgKp8CWPWI/lby3su8S2fYJ|discussion]] |
| Line 15: | Line 34: |
| * Robert Bradshaw * Jason Grout |
|
| Line 16: | Line 37: |
| * Alex Leon | * Alex Leone |
| Line 18: | Line 39: |
== Motivation == [[http://xkcd.com/844/|{{http://imgs.xkcd.com/comics/good_code.png}}]] |
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.
Scratch documents
Google Docs Scratchpad to keep track of tasks
Google Code Repositories
Tasks
- Write testing code to identify bottlenecks, and generally improve robustness.
- Convert notebook data structures to a database architecture to allow for concurrent scalable access to a centralized data store by different processes.
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.
Use mod_wsgi and Apache (say) to make the server scale massively.
Notes
Be aware of the sage-devel discussion.
- 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.
A proposal for a scalable server: google docs link and discussion
People
- Tom Boothby
- Robert Bradshaw
- Jason Grout
- Mike Hansen
- Alex Leone
- William Stein
Motivation
