But typically what you are looking for is the "number of operations"
per unit time. In the case of R, what you would probably be doing is
to monitor the time that it takes to go through a number of scenarios
and then divide this number by the CPU time and you will get "number
of operations per CPU
On Sun, 28 Oct 2007, kevinchang wrote:
>
> Hi all,
>
> Since proc.time return three different kind of times (user, system and
> elapsed) , I am wondering which one is right for calculating flops.
Probably none of them. The 'user'+'system' time is the amount of CPU time
that can be blamed on R.
You would want to use the "user" time since that indicates that amount
of time it spends in the user application, which would be R. Take a
look at the ratio between user and system; user should be much higher
than system. If not, then this might indicate that you have a lot of
I/O going on, or s
Hi all,
Since proc.time return three different kind of times (user, system and
elapsed) , I am wondering which one is right for calculating flops. In New S
Language (Becker et. al. ) , it seems to be the user because " the user time
measures the processor time used in S and the system time measu
4 matches
Mail list logo
