On Mar 3, 6:16 pm, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: > time echo "2+2;" | /absolute/path/to/sage >
For me: real 0m24.730s user 0m6.712s sys 0m1.884s real 0m5.127s user 0m4.348s sys 0m0.784s real 0m5.245s user 0m4.560s sys 0m0.840s It's a N270 atom netbook, my hdd is $ sudo hdparm -i /dev/sda Model=FUJITSU, FwRev=8909, SerialNo=K616T913TG79 [ ... a lot of blahhh ... it's pio4 and caching enabled ... ] In comparison, chrome starts ~1 second on first startup, hence there is a lot to improve. I think we should look at the list of all files that are read on startup and try to minimize them. That's the easiest way and probably also the most effective one. 4 seconds of processing time and 18 secs of harddisk seem to paint a clear picture who is to blaim. ;) Also, patterns like lazy creation of objects might help, especially when it reduces the number of file accesses. h -- 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
