On Wed, Feb 23, 2011 at 4:43 AM, Volker Braun <vbraun.n...@gmail.com> wrote: > I take it that the slow thing is reading ~2000 sage library files from a > harddisk into the filesystem cache. I'm using SSDs and Sage starts > consistently within about 1 second. There is "sage -startuptime" to profile. > The way I see it, the only way to make a significant dent into the startup > time is either psychological (show a prompt and read in the backgroupnd) or > save the whole Sage session into a single file on the first startup and read > it from there (can you pickle a python session? ;-)
I doubt all 2000 files need to be read into memory, probably only 20-30% of them do. A psychological improvement such as showing the prompt (with working tab completion) quickly would be a good thing as well, but not really solve the problem, especially for a cold start. - Robert -- 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
