My first guess would be something else is happening on disk at the same
time (or over the network), a 1.5% timing variation between runs is well
within that range. Run it multiple times if you're curious and get some
broader stats.
Also, gut feeling, try Kurian's code, but move the time.time() ca
@likage - Run them multiple times and average the results. With file
operations involved, you are bound to have variation.
On Wed, Jul 8, 2015 at 4:00 PM Kurian O.S wrote:
> And remember Justin is always right :D
>
Just a roll of the dice, actually.
>
> On Tue, Jul 7, 2015 at 8:59 PM, Kurian
I see, will keep a lookout again the next time when I tried to open another
big file.
Pretty sure that I am opening the file (each methods) in about the same
environment.
Aye' Sir - on your latest reply XD
On Wednesday, July 8, 2015 at 12:00:29 PM UTC+8, Kurian wrote:
>
> And remember Justin i
And remember Justin is always right :D
On Tue, Jul 7, 2015 at 8:59 PM, Kurian O.S wrote:
> There will be slight difference always based on the cpu usage, even like
> you have a vlc player playing can make a huge difference in the results :).
>
> On Tue, Jul 7, 2015 at 8:55 PM, likage wrote:
>
>
There will be slight difference always based on the cpu usage, even like
you have a vlc player playing can make a huge difference in the results :).
On Tue, Jul 7, 2015 at 8:55 PM, likage wrote:
> Thanks guys, that is what I am looking for :D
>
> Will take a look into Maya API though it may take
Thanks guys, that is what I am looking for :D
Will take a look into Maya API though it may take me a while to digest it
since I am not at all familiar with it.
I have a question though.
While using the 2 methods as suggested by Justin and Kurlan, the output
results that I have obtained from bo
