I agree that this looks strange. We once had a client that resetted the CPU time every time an App was suspended, so the total CPU time claimed was just the time since the last resume. Also some emulators (VMWare, Wine) sometimes give very confusing results concerning the CPU time. In any case I'd rather suspect the claimed CPU time being wrong han the result.
> I agree that this looks strange. We once had a client that resetted the CPU
> time every time an App was suspended, so the total CPU time claimed was just
> the time since the last resume. Also some emulators (VMWare, Wine) sometimes
> give very confusing results concerning the CPU time. In any case I'd rather
> suspect the claimed CPU time being wrong han the result.
Yep! you are right, when you look at the sequence of reporting times, the error seems in the used time.
This result looks pretty strange!
)
I agree that this looks strange. We once had a client that resetted the CPU time every time an App was suspended, so the total CPU time claimed was just the time since the last resume. Also some emulators (VMWare, Wine) sometimes give very confusing results concerning the CPU time. In any case I'd rather suspect the claimed CPU time being wrong han the result.
BM
BM
> I agree that this looks
)
> I agree that this looks strange. We once had a client that resetted the CPU
> time every time an App was suspended, so the total CPU time claimed was just
> the time since the last resume. Also some emulators (VMWare, Wine) sometimes
> give very confusing results concerning the CPU time. In any case I'd rather
> suspect the claimed CPU time being wrong han the result.
Yep! you are right, when you look at the sequence of reporting times, the error seems in the used time.