On Wed, May 20, 2015 at 9:48 AM, Irmen de Jong wrote:
> Or measure the actual CPU clock cycles taken instead of the wall clock run
> time.
> Then you should get a fairly constant number, if the program does the same
> work every
> time you run it.
>
> phobos:~ irmen$ time python test.py
> real
On 20-5-2015 17:23, Ian Kelly wrote:
> On Wed, May 20, 2015 at 7:02 AM, AKHIL RANA wrote:
>> Hi,
>>
>> I am student at IIT Kanpur and working on a Opencv based Python project. I
>> am working on program development which takes less time to execute. For that
>> i have tested my small program hello
On Wed, May 20, 2015 at 7:02 AM, AKHIL RANA wrote:
> Hi,
>
> I am student at IIT Kanpur and working on a Opencv based Python project. I
> am working on program development which takes less time to execute. For that
> i have tested my small program hello word on python to now the time taken by
> th
Hi,
I am student at IIT Kanpur and working on a Opencv based Python project. I
am working on program development which takes less time to execute. For
that i have tested my small program hello word on python to now the time
taken by this program. I had run many time. and every time it run it gives
