On Feb 13, 8:05 pm, juaninf <juan...@gmail.com> wrote: > thanks by your attention Volker, ... but this command return the > "cycles per second" measure?
If your processor is running at 2 GHz, it means it's doing 2 * 10^9 cycles per second. If sage is the only job that is using significant computing resources, then you can safely assume that nearly all those cycles are spent on the sage process. The time returned by timeit tries to compensate for time spent on other jobs, but the truth is that performance gets affected in very unpredictable ways if multiple jobs are making demands on computing resources. Cycles are a nearly meaningless measure of computing effort nowadays, though, given that they can be spent waiting on memory or that in one cycle multiple arithmetic operations might be taking place in the processor, thanks to the advanced out-of-order scheduling modern CPUs employ. The times you get back from "timeit" are probably one of the most consistent measures for computational complexity of computations (following the algorithms implemented in sage of course!). If you want to compensate for the relative power of the machine you're running on you could multiply with the (peak) clock frequency of the CPU to get "cycles spent" on computations, but I'd be surprised if that gives consistent results across different machines. There are too many other factors that play a role. -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
