In our setup some 5 years ago (we did a lab-based course for 200 undergraduates using Sage), if I recall right, we used one user for the notebook server, and a different user, "worker", to run computations; there were various ulimits on the latter account (one sometimes forgotten is a limit on the file size, as people tend to leave computations running and producing a lot of output...). One more trick: we did run "worker" with high niceness level, this makes the server more responsive.
On Sunday, November 27, 2016 at 11:04:48 AM UTC, Enrique Artal wrote: > > Thanks, As you say, it would be better something more direct, but your > approach is a strong improvement for my needs. > By the way, I changed in our experimental notebook 7.4 -> 7.3 and the > limits work: they stop the process and the notebook is still running. > > Enrique. > > El domingo, 27 de noviembre de 2016, 6:07:05 (UTC+1), [email protected] > escribió: >> >> On Sat, 26 Nov 2016, Enrique Artal wrote: >> >> > By the way, using server_pool, is there a way to know which user of the >> > notebook is using a user of the server_pool? >> >> AFAIK not really. I can list files in /tmp and run fuser for them, i.e. >> >> fuser /tmp/* >> >> and see, for example >> >> /tmp/tmpwIR2_j: 7589c >> >> and in that file I can see a line like >> >> DATA = . . . /sage_notebook.sagenb/home/jm58660 >> >> and hence user jm58660 is behind the process #7589. >> >> This could be scripted of course, but I would like to have better NB made >> as admin viewpoint in mind. >> >> -- >> Jori Mäntysalo > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
