[IPython-dev] Multi-user IPython Notebook

Brian Granger ellisonbg at gmail.com
Fri Oct 3 14:57:08 EDT 2014

(Kyle, working at Rackspace, might not volunteer this information in
this context)

I highly recommend looking at Rackspace's OnMetal Servers for
performance critical things that you want to cost contain.



On Fri, Oct 3, 2014 at 11:18 AM, ssanderson <ssanderson at quantopian.com> wrote:
> Kyle,
> Currently we're spinning up new containers manually over SSH using Fabric.
> The container we're running is conceptually pretty similar to the
> scipyserver container in  docker-notebook
> <https://github.com/ipython/docker-notebook>  .  At the moment we're not
> doing any sort of proxying, so each single user server just gets its own
> unique URL and password, which is supplied to its user.
> As far as how many containers we run per host, we're still playing around
> with different instance types and resource limits, so we haven't settled on
> a specific number.  One of the challenges for us is that different research
> activities have radically different performance profiles.  For example,
> querying historical financial data is mostly IO-bound, analyses of large
> datasets are often constrained by RAM, and backtesting with in-memory data
> is primarily CPU-bound (in my dream world, we can farm out the CPU-bound
> tasks to pool of worker containers using IPython Parallel, but that's a ways
> off).   That said, I think our current ballpark is to run on the order of 10
> containers per host.
> --
> View this message in context: http://python.6.x6.nabble.com/Multi-user-IPython-Notebook-tp5073520p5073582.html
> Sent from the IPython - Development mailing list archive at Nabble.com.
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev

Brian E. Granger
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger at calpoly.edu and ellisonbg at gmail.com

More information about the IPython-dev mailing list