Question #254856 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254856
Status: Open => Answered
RaiMan proposed the following answer:
ok, that are the values, we have to live with currently (up to version
1.1.0) in case of exists-not-found.
On my Win8-64 i7/3.4 (1920x1200) I get similar values with version 1.1
In version 1.2 I will add some optimization by dispatching chunks of
search into different threads, to better use multicore systems.
In 1.1.0 I have added find profiling, that internally stores the elapsed times
of the find ops with the Match and the search Region:
someMatch.getTime()
someRegion.getLastTime()
both return as long the duration in msecs of the last find op.
So this might make it a bit easier, if you are only interested in the elapsed
time consumed by a find op
Be aware: your last example: if not found, this is always the given wait time
(usually slightly larger)
(except exists(img,0), since this always returns after the first trial)
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.
_______________________________________________
Mailing list: https://launchpad.net/~sikuli-driver
Post to : [email protected]
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
