First of all, the "sage -startuptime" and the patchbot startuptime module are totally independent.
The output of "sage -startuptime" only lists the 50 slowest modules, not all. There is also a certain amount of luck in its output for individual modules, e.g. whether or not the globals() hash table is reallocated during the module import. Garbage collection is turned off, at least. On Tuesday, February 26, 2013 9:32:48 PM UTC-10, Simon King wrote: > > Hi! > > The patchbot's startup_time plugin complains about #14159. In order to > see what is happening, I studied the output of sage -startuptime, and > got a surprise. > > I have run `sage -startuptime` both with and without the patch. > > - Without the patch, the import of `_ssl` is listed with 3.397ms. But > with the patch, `_ssl` is not listed. > - With the patch, the import of `sage.plot.graphics` is listed with > 21.036ms. But without the patch, `sage.plot.graphics` is not listed. > > I can neither believe that `sage.plot.graphics` is not imported during > startup in vanilla sage, nor can I believe that `sage.plot.graphics` is > only imported since the intestines of coercion dictionaries change. > > Bug in the startuptime script? Or how can it be explained that > sage.plot.graphics was not listed for vanilla sage? > > Best regards, > Simon > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
