On Feb 12, 12:04 am, Jan Groenewald <j...@aims.ac.za> wrote:
> Hi
Hi Jan,
> 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)
Well, Timothy has written some code that makes this adjustable by the
notebook admin. The code remains in limbo for now and is unlikely to
make it into 3.3.
> - 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?
I swear I opened a ticket for that one, but I cannot find it. Fixing
this should be doable since even a primitive version would diff to the
previous snapshot and delete it of no differences were found. Not
making the snapshot is nothing changes would save IO and CPU cycles
and would be a much better solution. If someone finds the ticket
please let me know.
> - 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
> }
Well, that patch changes the default cell type, but the adjustment to
change the default autosave_interval is obvious. There is no ticket to
do so yet, but I think we should raise the autosave_interval to
something reasonable, i.e. 15 minutes. If we implement the snapshot
fix mentioned above we might not even need to adjust it for now.
In the past we had similar issues with the global notebook backup
being too frequent and this stemmed from way back when the notebook
server tended to crash. These days the save default is 24 hour IIRC.
> - 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.
Yes, that one is merged in 3.3.
> regards,
> Jan
Overall while looking for tickets related to the problem I am shocked
how many small and large usability tickets as well as bugs related to
the notebook are open. It seems like we should attempt to schedule a
bug day in about two weeks to concentrate on the notebook. Last time
William got pissed about the state of the notebook and the number of
open notebook issues he and others ended up fixing 50+ ticket in one
release cycle. It seems we do need this fury again :)
Given that this does not require deep mathematical skills it might be
time to troll for notebook developers, so making the open issues
accessible and easy to understand for newcomers and posting to sage-
support with a "looking for notebook dev" might be a good idea.
Cheers,
Michael
> --
> .~.
> /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
-~----------~----~----~----~------~----~------~--~---
