Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2010-11-20 22:21:25 →
Size: 745
Editor: TomBoothby
Comment:
← Revision 2 as of 2010-11-20 23:33:22 → ⇥
Size: 1048
Editor: was
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]].
Line 8: Line 8:
 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.
Line 16: Line 16:
 * Alex Leon  * Alex Leone

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.

People

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