> 1) Sun Blade 2000, circa 2000 > 2 x 900 MHz UltraSPARC III+ CPUs > Load average 1 (Sorry, I'm doing something and can't stop that) > 1x 147 GB Seagate SEAGATE-ST3146807FC. 15,000 rpm SCSI with a 2 Gbit/s fibre > channel interface. > Sage version 4.3.3 with patches for Solaris as documented at > http://trac.sagemath.org/sage_trac/ticket/8409 > Median of the 5 runs is: > sage: sage: > > Exiting SAGE (CPU time 0m0.17s, Wall time 0m0.19s). > > real 0m8.263s > user 0m6.502s > sys 0m1.392s > > Maximum time of the 5 runs is > real 0m8.356s > > Minimum tie of the 5 runs is > real 0m8.066s
> 2) Macbook Pro, circa 2009 > 2.66GHz Intel Core 2 Duo > Fairly loaded (Activity Monitor reports about 70% idle CPU, 635MB/4GB free > memory) > > Median time of 5 runs: > real 0m2.390s > Maximum of the 5 runs: > real 0m22.064s 3) Mobile Intel(R) Pentium(R) III CPU - M 1000MHz, idle, 256 MB Median time of 5 runs: real 0m7.632s Maximum of the 5 runs: real 0m34.508s Time goes down to 0m5.211s, but for me only the time of the first start is important. I do not see any usecase where I'd start and quit sage 5 times in a row. For comparison, FriCAS takes only 0m0.797s on this machine. Martin -- 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
