On Thu, Oct 29, 2009 at 10:29 AM, Jason Grout <[email protected]> wrote: > hmmm...instead of world-writeable, you could also make the tmp directory > group-writeable and make the server and worksheet members of the same group.
Given that the only users in the virtual machine are the worksheet processes and notebook process, that would be pointless. > So you make a new temporary directory every time a cell is evaluated, > and these copies are done? Wow. No wonder you want this to be a RAM disk. On a local Linux filesystem (i.e., not some badly configured NSF mount), using a RAM disk or not for such things makes essentially no difference, since *everything* happens in RAM until the net result is flushed to disk when sync is called every so often. Lately I have switched to putting the Sage install itself on a RAM disk though, since that speeds Sage startup time. Speaking of startup time, I'm sad that numpy, matplotlib, etc., all get imported by default again, hence "sage -startuptime" is bad again. We need to stop having all those slow-to-import modules get imported by default once and for all (by adding and keeping doctests around that verify that these modules aren't imported). -- William --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
