Question #668161 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/668161
Status: Open => Answered
RaiMan proposed the following answer:
Profiling SikuliX scripts usually does not make sense, since the timing
mainly depends on the reaction of the GUI. In many cases SikuliX scripts
are even too fast, so one has to insert additional waits or image
searches to synchronize the workflow.
If one thinks, that a workflow runs too slow, then the only available
optimization is to take care, that the search region is made as small as
possible. Compared to the whole screen as search region an search region
that is not much larger than the searched image, will usually reduce the
reaction time from about 1 second down to about 100 msecs on average.
Any profiling tool used from a command line must be compatible with Jython (I
do not have any experiences).
Another option might be to use Eclipse/PyDev or PyCharm.
SikuliX itself does not have any feature about that, apart from
debugging with timestamps.
--
You received this question notification because your team Sikuli Drivers
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
