Re: [sage-devel] Jupyterhub kernel and SAGE_ROOT

2018-11-16 Thread Luca De Feo
> I guess that 50 simultaneous connection will be the maximum. The use might
> be, for example, a course on graph theory having mandatory but trivial
> exercise about SageMath graph functions.

That's a reasonable load.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Jupyterhub kernel and SAGE_ROOT

2018-11-16 Thread Jori Mäntysalo

On Fri, 16 Nov 2018, Luca De Feo wrote:


and maybe 10 of them will be heavy duty users. Then maybe 500 may
be users in some random course, or checking just one computation etc.


500 hundred simultaneous connections may also be a bit too much,
depending on how powerful your server is.


I guess that 50 simultaneous connection will be the maximum. The use might 
be, for example, a course on graph theory having mandatory but trivial 
exercise about SageMath graph functions.


--
Jori Mäntysalo

Re: [sage-devel] Jupyterhub kernel and SAGE_ROOT

2018-11-16 Thread Luca De Feo
> How fast will new SageMath versions be packaged? I suppose that fast
> enought, and those needing the bleeding edge version can compile it
> themself.

I agree. Ubuntu bionic has 8.1, cosmic has 8.3.

Unless we screw up and make Sage impossible to package (see mail by
Samuel on Debian freeze), these will follow closely enough for the
average user.

> Seems interesting. Here we will have about 35,000 theoretically possible
> users,

That's a lot for a single server! Unless the average use is a single
day a year :)

> and maybe 10 of them will be heavy duty users. Then maybe 500 may
> be users in some random course, or checking just one computation etc.

500 hundred simultaneous connections may also be a bit too much,
depending on how powerful your server is.

> I have no previous experience on containers, but I guess they are here to
> stay and I should learn them.

I got to the point where I consider Docker as fundamental a tool  as Git.

Luca

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: NTL 11.3.2

2018-11-16 Thread Samuel Lelievre


Le vendredi 16 novembre 2018 02:44:17 UTC+1, Victor Shoup a écrit :
>
> I just uploaded NTL 11.3.2 to https://www.shoup.net/ntl/
>
> This fixes a performance issue in the ZZ PowerMod function (which also 
> affects the prime testing and generating function).
>

The upgrade in Sage is tracked at
https://trac.sagemath.org/ticket/25532

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Jupyterhub kernel and SAGE_ROOT

2018-11-16 Thread Jori Mäntysalo

On Mon, 5 Nov 2018, Luca De Feo wrote:


Packagers have already solved it for various distributions, so, if you
don't need a Sage version compiled from sources, you can have a
working Sage + JupyterHub setup using the system packages with no
further hacks.


How fast will new SageMath versions be packaged? I suppose that fast 
enought, and those needing the bleeding edge version can compile it 
themself.



I have a blog post on the whole process of setting up JupyterHub using
Docker Compose (spoiler: it's easy):

 https://opendreamkit.org/2018/10/17/jupyterhub-docker/


Seems interesting. Here we will have about 35,000 theoretically possible 
users, and maybe 10 of them will be heavy duty users. Then maybe 500 may 
be users in some random course, or checking just one computation etc.


I have no previous experience on containers, but I guess they are here to 
stay and I should learn them.


--
Jori Mäntysalo