sikuli-driver team mailing list archive

[RaiMan <question240917@xxxxxxxxxxxxxxxxxxxxx>]

Question #240917 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/240917

    Status: Open => Answered

RaiMan proposed the following answer:
the relevant setting is
Settings.WaitScanRate

with a default value of 3, which means 3 searches per second with an
updated screenshot

With large monitors (around 2Kx2K) the average search time with medium
speed machines should be calculated with about 0.5 seconds (where about
2/3 internally is spent on the conversion of the screenshot (in memory
BufferedImage) to an OpenCV Mat object (this is an annoyance and I will
try to find a faster solution for that next year), which in turn is used
to finally search the given (usually small) image)

So on large monitors you will have a situation with rather high cpu
usage, when always searching on the whole screen, since Sikuli will be
searching something in average (which internally is completely number
crunching).

So the general recommendation with Sikuli workflows is to as often as
possible try to search in restricted regions on the screen, which can be
evaluated relative to known matches using the many available Sikuli
features in class Region.

You might set the above mentioned value to higher values (more searches
per second, only makes sense if you very often use small regions) or to
lower values (<1 is possible) to slow down the repeated search (which
saves cpu).

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.