On Tue, Feb 11, 2014 at 3:11 PM, Volker Braun <vbraun.n...@gmail.com> wrote: > Hi Willam, > > That wasn't me, I worked on caching the imports on startup (which > includes a lot of attempts to load modules in the wrong path). But to > really use that we'd need a reliable way to regenerate the cache, > presumably during the library build (sage -br). > > The Sage doctest framework works by forking a once-started Sage > session, for the record. Its not particularly complicated. > > All things considered, I don't think that startuptime is a problem right now: > > $ time echo quit | sage > [...] > sage: Exiting Sage (CPU time 0m0.01s, Wall time 0m0.01s). > > real 0m1.150s > user 0m0.755s > sys 0m0.153s
Cool -- is that with an SSD and warm cache? I get about 2 seconds everywhere on SageMathCloud with sage-5.12 right now. We're very likely switching all of (the UW part of) SageMathCloud to SSD's in the near future though. And yes 1-2 seconds is pretty reasonable. But 0.25 would be better... -- William > > On Tue, Feb 11, 2014 at 9:33 PM, William Stein <wst...@gmail.com> wrote: >> Hi Volker, >> >> I think you wrote a forking command line Sage daemon a while ago. >> What's the status of that? I was just discussing Sage startup time >> with Andrew Ohana and he wasn't aware of it... >> >> William >> >> -- >> William Stein >> Professor of Mathematics >> University of Washington >> http://wstein.org -- William Stein Professor of Mathematics University of Washington http://wstein.org -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
