Use timeit to benchmark:
sage: timeit('1+1')
625 loops, best of 3: 729 ns per loop
"man time" will explain real/user/sys if you want to know:
The time command runs the specified program command with the
given arguments. When command
finishes, time writes a message to standard error giving timing
statistics about this program
run. These statistics consist of (i) the elapsed real time between
invocation and termination,
(ii) the user CPU time (the sum of the tms_utime and tms_cutime
values in a struct tms as
returned by times(2)), and (iii) the system CPU time (the sum of
the tms_stime and tms_cstime
values in a struct tms as returned by times(2)).
On Wednesday, July 31, 2013 10:33:07 PM UTC-4, Verónica Suaste wrote:
>
> Hi,
>
> I want to compare different algorithms in terms of time.
> When I put %time I get these three data as output CPU times, sys and wall
> time. Somebody can explain me(or suggest a link) what it means each one,
> and how should I consider each one for comparisson?
>
> Thanks!
> Verónica
>
--
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.
