> This afternoon, William gave me a really cool idea of starting up Sage > using fork(). Essentially you have one mothersage which forks off > copies of Sage. Like this, you can get an instant Sage prompt because > Sage is already started. I actually implemented this and it seems to > work (at least under Linux, I haven't tested other systems).
FWIW it seems to work fine on OS X 10.6. > I'm not sure how robust it is, but if you want to play with it, you can > find the code at http://sage.math.washington.edu/home/jdemeyer/forker/ > > > First of all, you need to compile > $ gcc fsage.c -o fsage > > > Then, start up the mothersage: > $ sage > ---------------------------------------------------------------------- > | Sage Version 4.6.1, Release Date: 2011-01-11 | > | Type notebook() for the GUI, and license() for information. | > ---------------------------------------------------------------------- > sage: load "sage-forker.pyx" > Compiling ./sage-forker.pyx... > sage: sage_forker() > > > Now open a new terminal and watch the Sage prompt appear without delay: > $ ./fsage > ---------------------------------------------------------------------- > | Sage Version 4.6.1, Release Date: 2011-01-11 | > | Type notebook() for the GUI, and license() for information. | > ---------------------------------------------------------------------- > sage: Sort of a tty server instead of a notebook server. > Have fun with it and who knows if this might actually be useful. > > Jeroen. I'm not sure I completely understand the code, but it looks like this can't be used to speed up `sage -c`, is that right? -Ivan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
