On 10/21/11 10:32 AM, William Stein wrote:
On Thu, Oct 20, 2011 at 11:39 AM, Jason Grout
<[email protected]> wrote:
On 10/20/11 1:02 PM, William Stein wrote:
On Thu, Oct 20, 2011 at 8:31 AM, Jason Grout
<[email protected]> wrote:
On 10/20/11 10:07 AM, MichTex wrote:
Thanks! It is back up, although it is still very slow. I'm guessing
that it has a heavy load already.
The load isn't particularly heavy---only about 8 people. It was handling
a
much bigger load yesterday, for example. The server was even slow
serving
up the webpage when I tried to get it from the computer the server is
running on, so I'm not sure what is going on. I restarted it once more
and
it seems fine now. Let us know if it gets slow again.
It got very slow again and I'm restarting it. I'm worried that has
something to do with what you (Jason) did, e.g., switching to twisted
11?
The recent changes certainly seem like the most likely culprit. Switching
back to the old versionis should be as easy as switching one symbolic link
to point to sage-4.7 instead of sage-4.7.1:
cd /sagenb/sage_install/
rm sage_sagenb
ln -s sage sage_sagenb
and then restarting sagenb.
Instead I just commented these two lines out of the admin script:
#elif self.name == 'sage_notebook-sagenb':
# sage = 'sage-sagenb'
Yes, that would work too.
then did
sagenb@mod:~/servers$ ./admin --restart=sagenb
Instantly after doing this *demo* became much faster.
I noticed before doing this that there was a single sagenb server
Python process running in top using a lot of cpu..
Okay, then it certainly does point to kcrisman's conclusion. I'll see
if I can diagnose the problem, but probably won't have time to do so
until early next week.
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
