Puzzle: Why does it take nearly **twice as long** to just run sage and exit
as it does to import the sage library and run a command? Timings below are
on an SSD:
~$ time sage -python -c "import sage.all; sage.all.factor(2018)"
real 0m2.795s
user 0m2.296s
sys 0m0.276s
~$ time echo "factor(2018)" | sage
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 8.0, Release Date: 2017-07-21
│
│ Enhanced for CoCalc.
│
└────────────────────────────────────────────────────────────────────┘
In [1]:
2 * 1009
In [2]: Exiting Sage (CPU time 0m0.02s, Wall time 0m0.03s).
real 0m4.676s
user 0m3.852s
sys 0m0.392s
—
My guesses:
- IPython has got very bloated over the years and takes a long time to start?
- Something dumb involving how the sage-cleaner processes is spawned?
- Our code to print the banner is dumb?
— William
--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
