Hi

Our students are going over disk space quota due to the large
amounts of snapshots kept by the notebook. 

(They have 512M home dir quota and .sage has grown to between 60M and
120M for all of them after 3 weeks of intensive use. In one case sage
could not save the notebook objects correctly due to quota freeze, and it is now
too corrupted to start. He will probably manually restore worksheets,
quite a pain.)

Some suggestions on #sage-devel were:

- On our system set notebook timetout to something other than 0.
(probably not applicable as a default for sage)

- do not save snapshots when nothing has changed.
(probably easy and quick to do as a default for sage?)
Is there a ticket? Can one be created?

- apparently a patch for a more sensible autosave_interval
and max_history_length already exists and will NOT be in 3.3.
Perhaps this ticket can be bumped to go in soon:
 diff -r b0aa7ef45b3c sage/server/notebook/user_conf.py
 --- a/sage/server/notebook/user_conf.py Mon Jan 05 23:03:45 2009 -0800
 +++ b/sage/server/notebook/user_conf.py Wed Feb 11 08:58:59 2009 -0800
 @@ -4,7 +4,7 @@
  import conf
  defaults = {'max_history_length':500,
 -            'default_system':'sage',
 +            'default_system':'python',
              'autosave_interval':3*60,   # (in seconds)
              'default_pretty_print': False
              }

- apparently the interact bug (all worksheets containing interact
open and start running when notebook opens) will be fixed in 3.3,
and this will alleviate some of the problem.

regards,
Jan


-- 
   .~. 
   /V\     Jan Groenewald
  /( )\    www.aims.ac.za
  ^^-^^ 
Teach with sage: http://www.aims.ac.za/english/courseguidelines.php

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to