On 10/27/11 12:56 PM, William Stein wrote:
That's probably because there are over 500 simultaneous open worksheets right now. I've reset the servers but it will probably get heavily loaded again soon enough. Obviously we need to start planning for the next level in scalability...
I wonder if switching from the simple twistd server to, say, nginx serving flask, would help things in the short term. I notice that the sagenb.org process (given by the PID listed in the ./admin --status command) hovers around 50-70% CPU utilization. That seems like a lot.
Thanks, Jason -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
